← previous blocknext block →recent activity
Analyzing
Block #76,196,617
15 transactions · 13 stateful · 2026-05-22 05:19:47 UTC
Parallelism
73/100
Blocked
31%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,196,617 · 15 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
1w08w010w112w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x0d63ff4f…4f9a
0x34b655…2a6f
6 touches
3 conflicts
0xff57dec4…6482
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x802741e7…56b9
0x34b655…2a6f
4 touches
1 conflict
0x9fc6ea79…e2dc
0x34b655…2a6f
4 touches
1 conflict
0xc56d6548…50a4
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