← previous blocknext block →recent activity
Analyzing
Block #76,198,777
11 transactions · 9 stateful · 2026-05-22 05:34:07 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,198,777 · 11 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x57c3a64f…2e64
0x065c9d…c394
4 touches
1 conflict
0xfc3f1f0c…dc3e
0x065c9d…c394
4 touches
1 conflict
0xb675486b…b014
0x065c9d…c394
2 touches
0 conflicts
0xf3d7a307…4d63
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0002
0x08dd3d…a583
2 touches
0 conflicts
0xff9eec93…1598
0x08dd3d…a583
2 touches
0 conflicts
0x00000000…0003
0x0a4fcb…a602
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity