← previous blocknext block →recent activity
Analyzing
Block #72,817,709
23 transactions · 21 stateful · 2026-05-06 13:30:43 UTC
Parallelism
74/100
Blocked
57%
Avg conflicts / tx
1.04
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #72,817,709 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w39w010w111w212w314w015w116w219w220w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x7e9d3a…9fda
8 touches
6 conflicts
0xbb975a6c…bff4
0x34b655…2a6f
6 touches
3 conflicts
0xb179e4c1…e2d0
0xd32edf…ff58
5 touches
3 conflicts
0x6f2e60dc…e661
0x34b655…2a6f
4 touches
1 conflict
0x7fdf0ab6…14eb
0x34b655…2a6f
4 touches
1 conflict
0xaf498679…7732
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity