← previous blocknext block →recent activity
Analyzing
Block #76,112,612
21 transactions · 17 stateful · 2026-05-21 20:00:22 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #76,112,612 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w07w38w49w010w115w416w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99a21305…dffc
0x2a68ba…90c5
10 touches
10 conflicts
0x41755291…977f
0x065c9d…c394
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x4525ab03…8bb7
0x065c9d…c394
7 touches
6 conflicts
0x17b3e52d…6837
0x5afd3e…7620
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x00000000…0005
0x5afd3e…7620
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
10 conflicts on slot 0x99a2130578…57dffc
Audit this contract →
← previous block·next block →recent activity