pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,260,008
← previous block
next block →
recent activity
Analyzing
Block #74,260,008
16 transactions · 8 stateful · 2026-05-13 05:47:17 UTC
Parallelism
88
/100
Blocked
13
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,260,008
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swap
· blocks 1
#3
swap
#4
swap
#5
swap
#6
swap
#7
swap
#8
swap
#9
swap
#10
swap
#11
forward
#12
updateDataFeedsValuesPartial
#13
updateDataFeedsValuesPartial
#14
0x6a0410dc
#15
setData
#2
swap
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0x398e3d…298c
4 touches
1 conflict
0x00000000…000c
0x398e3d…298c
4 touches
1 conflict
0x9ef62133…9b47
0x3bd359…433a
4 touches
1 conflict
0xa282f848…de55
0x000000…012a
4 touches
1 conflict
0xf6802cf0…344f
0x000000…012a
4 touches
1 conflict
0x00000000…0001
0x398e3d…298c
4 touches
1 conflict
0x00000000…0002
0x398e3d…298c
4 touches
1 conflict
0x68faa0b9…14af
0x368ee5…7ca4
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:
0x398e3d74…e2298c
1 conflict on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity