pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#74,423,152
← previous block
next block →
recent activity
Analyzing
Block #74,423,152
12 transactions · 12 stateful · 2026-05-13 23:52:43 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.42
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,423,152
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xa96df62f
#2
0x1ffa3c9b
· blocks 3
#5
0x39435dac
#6
updateDataFeedsValuesPartial
#7
0x98717539
#8
setData
#9
forward
#11
0x39435dac
#3
0x1ffa3c9b
· blocks 2
#4
0xed82b078
#10
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffe431af…8faa
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x7d81a5d2…11c5
0x065c9d…c394
4 touches
2 conflicts
0x50997ada…364d
0x5d823e…89c6
4 touches
1 conflict
0xf0f673fd…37a7
0x5d823e…89c6
4 touches
1 conflict
0x6b319071…a105
0xc8689a…ee79
4 touches
1 conflict
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0x608e90f4…facf
0x065c9d…c394
4 touches
1 conflict
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:
0x065c9d28…a9c394
3 conflicts on slot
0xffe431af56…838faa
Audit this contract →
← previous block
·
next block →
recent activity