pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,261,233
11 transactions · 11 stateful · 2026-05-08 14:42:33 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,261,233 · 11 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
1w02w03w14w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x0b390c61…dc07
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0x8d0dfe2c…3345
0x2a68ba…90c5
4 touches
1 conflict
0xfbd3330b…a52b
0x065c9d…c394
3 touches
1 conflict
0xa633649b…2a63
0x065c9d…c394
3 touches
1 conflict
0x89dc96ec…702d
0x065c9d…c394
3 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: 0x065c9d28…a9c394
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity