pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,204,656
13 transactions · 12 stateful · 2026-05-08 08:26:19 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,204,656 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w27w08w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0xbdb374ba…2eb9
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xe688b749…6294
0x065c9d…c394
3 touches
1 conflict
0x330d0575…98e1
0x065c9d…c394
3 touches
1 conflict
0x7d614cb6…268a
0x065c9d…c394
2 touches
0 conflicts
0x98057fdb…304d
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: 0xab35264b…1cfa38
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity