pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,336,031
← previous block
next block →
recent activity
Analyzing
Block #73,336,031
8 transactions · 5 stateful · 2026-05-08 23:00:18 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,336,031
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x9036287a
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x69fe6b7a
#5
0xeffdedb0
#6
setData
#7
0xd9444a…6aef
#2
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d0dfe2c…3345
0x2a68ba…90c5
4 touches
1 conflict
0xbdff944d…447e
0x2a68ba…90c5
4 touches
1 conflict
0x3e4b8d9f…b8a7
0xaba216…a862
4 touches
1 conflict
0xc5564f8e…f4bf
0xaba216…a862
4 touches
1 conflict
0xd821ae10…fe17
0xc8689a…ee79
4 touches
1 conflict
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0e9f17dd…a6c0
0x065c9d…c394
3 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:
Kuru Exchange: MarginAccount
1 conflict on slot
0x8d0dfe2c6c…173345
Audit this contract →
← previous block
·
next block →
recent activity