pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,744,772
← previous block
next block →
recent activity
Analyzing
Block #73,744,772
7 transactions · 5 stateful · 2026-05-10 20:30:36 UTC
Parallelism
71
/100
Blocked
20
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,744,772
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
· blocks 1
#2
updateDataFeedsValuesPartial
#4
handleOps
#5
0xbe70473d
#6
setData
#3
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8dd3efb0…8445
0x34b655…2a6f
4 touches
1 conflict
0xadc53c77…bd1d
0x34b655…2a6f
4 touches
1 conflict
0xb245fe36…d765
0x34b655…2a6f
4 touches
1 conflict
0xb91a6f59…722c
0x34b655…2a6f
4 touches
1 conflict
0x56f8b3c0…8a5e
0x34b655…2a6f
4 touches
1 conflict
0x4bb80415…b7ed
0x34b655…2a6f
4 touches
1 conflict
0xaa8a1c54…ead3
0x34b655…2a6f
4 touches
1 conflict
0x97b6fa7b…0d6a
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
0x8dd3efb075…728445
Audit this contract →
← previous block
·
next block →
recent activity