pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#72,099,183
← previous block
next block →
recent activity
Analyzing
Block #72,099,183
10 transactions · 10 stateful · 2026-05-03 05:36:00 UTC
Parallelism
70
/100
Blocked
30
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,099,183
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x69f6df38
#2
revealWithCallback
#3
updatePrices
· blocks 2
#6
setData
#7
0x3f5c179b
· blocks 1
#9
0x39435dac
#4
updatePrices
· blocks 1
#8
0xed82b078
#5
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x7e9d3a…9fda
6 touches
3 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x004519fc…edaa
0x065c9d…c394
2 touches
0 conflicts
0x24968e6d…0132
0x065c9d…c394
2 touches
0 conflicts
0x2497f4c6…110e
0x065c9d…c394
2 touches
0 conflicts
0x75218c7e…26bd
0x065c9d…c394
2 touches
0 conflicts
0x8da60ea0…658a
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:
0x7e9d3a8a…4f9fda
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity