← previous blocknext block →recent activity
Analyzing
Block #76,213,721
14 transactions · 11 stateful · 2026-05-22 07:13:33 UTC
Parallelism
86/100
Blocked
18%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,213,721 · 14 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
2w03w04w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x10673ab0…8cd3
0x065c9d…c394
2 touches
0 conflicts
0x39453d2f…140b
0x065c9d…c394
2 touches
0 conflicts
0xb901c7a6…ec99
0x065c9d…c394
2 touches
0 conflicts
0xeecee9f4…b046
0x065c9d…c394
2 touches
0 conflicts
0xf2698576…ebb4
0x065c9d…c394
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: Market-MON/USDC
1 conflict on slot 0xf3d7a307cc…f14d63
Audit this contract →
← previous block·next block →recent activity