pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,816,925
← previous block
next block →
recent activity
Analyzing
Block #73,816,925
9 transactions · 7 stateful · 2026-05-11 04:36:14 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,816,925
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x719d975a
#4
0x6a015d36
#6
setData
#7
updateDataFeedsValuesPartial
#8
0x39435dac
#2
0x0c7abd22
· blocks 1
#5
0x13572d0b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x4efa90b3…d307
0x754704…b603
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xaa625301…4537
0x000000…012a
4 touches
1 conflict
0x00000000…000c
0x5e5e5f…7924
4 touches
1 conflict
0x00000000…0004
0x5e5e5f…7924
4 touches
1 conflict
0x00000000…0002
0x5e5e5f…7924
4 touches
1 conflict
0x00000000…0001
0x5e5e5f…7924
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:
0x1b68626d…2de19c
1 conflict on slot
0x0000000000…000013
Audit this contract →
← previous block
·
next block →
recent activity