pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,869,077
← previous block
next block →
recent activity
Analyzing
Block #73,869,077
11 transactions · 7 stateful · 2026-05-11 10:23:42 UTC
Parallelism
82
/100
Blocked
29
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,869,077
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0x40e79b1b
#4
0x000000b2
#6
forward
#7
0xed82b078
#8
mint
· blocks 1
#10
setData
#5
0x0c7abd22
#9
mint
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x93afca4c…b478
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0007
0x1414f3…5137
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x617a8835…88c4
0xd32edf…ff58
3 touches
1 conflict
0x01bfd454…8180
0x065c9d…c394
2 touches
0 conflicts
0x2c52fa84…cd65
0x065c9d…c394
2 touches
0 conflicts
0x593be5d5…b56b
0x065c9d…c394
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:
0x1b68626d…2de19c
1 conflict on slot
0x0000000000…000015
Audit this contract →
← previous block
·
next block →
recent activity