pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,202,362
← previous block
next block →
recent activity
Analyzing
Block #73,202,362
11 transactions · 9 stateful · 2026-05-08 08:11:04 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,202,362
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69fd9b10
#2
0x69fd9b10
#3
updatePrices
· blocks 1
#4
updatePrices
#6
updateDataFeedsValuesPartial
#7
0xeffdedb0
#8
setData
#9
0x39435dac
· blocks 1
#5
updatePrices
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x3b8ffd61…f3ad
0x34b655…2a6f
4 touches
1 conflict
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x3817764d…242b
0x34b655…2a6f
2 touches
0 conflicts
0x9254fd13…7d35
0x34b655…2a6f
2 touches
0 conflicts
0x97b0b2ee…4666
0x34b655…2a6f
2 touches
0 conflicts
0xa5fb9779…2384
0x34b655…2a6f
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer:
0xab35264b…1cfa38
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity