pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,924,912
← previous block
next block →
recent activity
Analyzing
Block #73,924,912
9 transactions · 5 stateful · 2026-05-11 16:35:38 UTC
Parallelism
78
/100
Blocked
20
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,924,912
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x39435dac
· blocks 1
#3
updateTemporalNumericValuesV1
#5
updateDataFeedsValuesPartial
#6
0x6a0205d2
#7
setData
#8
withdraw
#4
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0x8a85cf3d…2868
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0d97f8e9…658e
0x34b655…2a6f
2 touches
0 conflicts
0x28933977…81c5
0x34b655…2a6f
2 touches
0 conflicts
0x2aef4269…ad47
0x34b655…2a6f
2 touches
0 conflicts
0x4979f562…9051
0x34b655…2a6f
2 touches
0 conflicts
0x6f6fc26c…3e34
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:
Perpl
1 conflict on slot
0xf6476f21e7…f83580
Audit this contract →
← previous block
·
next block →
recent activity