← previous blocknext block →recent activity
Analyzing
Block #76,226,813
12 transactions · 10 stateful · 2026-05-22 08:41:04 UTC
Parallelism
83/100
Blocked
30%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,226,813 · 12 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
1w03w05w16w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x56f36365…7c40
0x065c9d…c394
2 touches
0 conflicts
0x6a164e0d…2bf4
0x065c9d…c394
2 touches
0 conflicts
0xc2756ff4…7cb8
0x065c9d…c394
2 touches
0 conflicts
0xd66b6513…cf2f
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity