← previous blocknext block →recent activity
Analyzing
Block #76,167,172
16 transactions · 13 stateful · 2026-05-22 02:03:47 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,167,172 · 16 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
1w02w15w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5bfc8fb…071f
0x2a68ba…90c5
4 touches
1 conflict
0x7609bf39…bbeb
0xa6afd3…d132
4 touches
1 conflict
0x42f03e67…ac31
0xa6afd3…d132
4 touches
1 conflict
0x15dfc675…c5e2
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xf9b8ae99…32b4
0x34b655…2a6f
4 touches
1 conflict
0xf9b8ae99…32b3
0x34b655…2a6f
4 touches
1 conflict
0x3bb96a58…6faf
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: Kuru Exchange: MarginAccount
1 conflict on slot 0xd5bfc8fb99…70071f
Audit this contract →
← previous block·next block →recent activity