pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,973,944
← previous block
next block →
recent activity
Analyzing
Block #72,973,944
9 transactions · 8 stateful · 2026-05-07 06:51:03 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,944
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69fc36ce
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x5bf9264c
#5
0x98717539
· blocks 1
#6
setData
#7
0xeffdedb0
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0x41f7d83d…143e
0x34b655…2a6f
4 touches
1 conflict
0x19725b1a…2b93
0x34b655…2a6f
4 touches
1 conflict
0xf4730a2d…3538
0x34b655…2a6f
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
2 touches
0 conflicts
0x0eac6378…36f4
0x34b655…2a6f
2 touches
0 conflicts
0x150af51d…9c42
0x34b655…2a6f
2 touches
0 conflicts
0xea02471d…1539
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
0x2877f4400c…13c2c8
Audit this contract →
← previous block
·
next block →
recent activity