← previous blocknext block →recent activity
Analyzing
Block #71,559,569
8 transactions · 6 stateful · 2026-04-30 17:43:41 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,559,569 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc683230…6df3
0x34b655…2a6f
4 touches
1 conflict
0xb9868b52…c77f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x17a10e05…3e1c
0x34b655…2a6f
2 touches
0 conflicts
0x5d32a251…d929
0x34b655…2a6f
2 touches
0 conflicts
0xb91a6f59…722c
0x34b655…2a6f
2 touches
0 conflicts
0xbb12db23…857e
0x34b655…2a6f
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: Perpl
1 conflict on slot 0xdc683230c0…216df3
Audit this contract →
← previous block·next block →recent activity