pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,183,032
← previous block
next block →
recent activity
Analyzing
Block #74,183,032
11 transactions · 9 stateful · 2026-05-12 21:15:32 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,183,032
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute302
#2
execute
#3
updateDataFeedsValuesPartial
#4
setData
#5
0x39435dac
#6
0x39435dac
#7
0x39435dac
#8
0x39435dac
#9
0x39435dac
· blocks 1
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x768cffcd…2648
0x34b655…2a6f
4 touches
1 conflict
0xaf5c6f0f…cba6
0x34b655…2a6f
4 touches
1 conflict
0xb6aedce9…a483
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1b159f3d…9163
0x34b655…2a6f
3 touches
1 conflict
0x00000000…0003
0xca50b9…1d03
2 touches
0 conflicts
0x00000000…0004
0xca50b9…1d03
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:
Perpl
1 conflict on slot
0xea02471df2…601542
Audit this contract →
← previous block
·
next block →
recent activity