← previous blocknext block →recent activity
Analyzing
Block #76,240,615
15 transactions · 13 stateful · 2026-05-22 10:13:01 UTC
Parallelism
87/100
Blocked
23%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,240,615 · 15 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
1w02w03w15w06w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3e49348b…9445
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x14cbac29…2179
0x065c9d…c394
2 touches
0 conflicts
0x27e56714…14ef
0x065c9d…c394
2 touches
0 conflicts
0x45288189…f437
0x065c9d…c394
2 touches
0 conflicts
0x9a4ae3c8…7eb1
0x065c9d…c394
2 touches
0 conflicts
0xba177b88…d016
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