← previous blocknext block →recent activity
Analyzing
Block #76,482,167
15 transactions · 14 stateful · 2026-05-23 13:01:11 UTC
Parallelism
73/100
Blocked
21%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,482,167 · 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
1w07w18w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0xd79bdaa3…b8bd
0x065c9d…c394
4 touches
1 conflict
0xf853eb8e…401e
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…000b
0x44b9e5…6477
2 touches
0 conflicts
0x00000000…003a
0x54fc07…e57e
2 touches
0 conflicts
0xa05ce891…d5f3
0x54fc07…e57e
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: Kuru Exchange: MarginAccount
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity