pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,036,415
← previous block
next block →
recent activity
Analyzing
Block #73,036,415
11 transactions · 10 stateful · 2026-05-07 13:46:53 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,036,415
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
0x121eab2f
· blocks 1
#5
poke
#6
updateDataFeedsValuesPartial
#7
markGameAsLost
#8
0xeffdedb0
#9
setData
#10
0x39435dac
#2
updatePrices
#4
0x121eab2f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd574ca…7ab1
4 touches
1 conflict
0x0175b7a6…1db9
0x6ca43f…c331
4 touches
1 conflict
0x0175b7a6…1dbb
0x6ca43f…c331
4 touches
1 conflict
0x0175b7a6…1dbd
0x6ca43f…c331
4 touches
1 conflict
0x1a4b4152…0a08
0x6ca43f…c331
4 touches
1 conflict
0x3e4b8d9f…b8a7
0x6ca43f…c331
4 touches
1 conflict
0x4e5ebbf7…ae70
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
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:
0xd574cae5…037ab1
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity