pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,973,539
← previous block
next block →
recent activity
Analyzing
Block #72,973,539
9 transactions · 8 stateful · 2026-05-07 06:48:21 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,973,539
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
requestRedeem
#2
updateDataFeedsValuesPartial
#3
0x39abec6b
#4
0x39435dac
· blocks 1
#5
0x69fc362d
#6
0xeffdedb0
#7
setData
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0105ce08…4920
0x2ab50b…5c41
2 touches
0 conflicts
0x0134444b…cd57
0x2ab50b…5c41
2 touches
0 conflicts
0x0230870e…327e
0x2ab50b…5c41
2 touches
0 conflicts
0x04077f86…d5fd
0x2ab50b…5c41
2 touches
0 conflicts
0x07d64d54…6bfc
0x2ab50b…5c41
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity