pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,209,634
16 transactions · 13 stateful · 2026-05-03 17:53:56 UTC
Parallelism
75/100
Blocked
46%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,209,634 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w07w111w212w213w014w115w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x48fb5c0f…3329
0xd32edf…ff58
7 touches
6 conflicts
0x510fb8ec…f6ea
0x065c9d…c394
5 touches
3 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…0002
0xa7283d…0ace
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x536e2740…61ac
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
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: 0xd32edf66…9fff58
6 conflicts on slot 0x48fb5c0fd1…a93329
Audit this contract →
← previous block·next block →recent activity