← previous blocknext block →recent activity
Analyzing
Block #76,111,916
10 transactions · 9 stateful · 2026-05-21 19:55:43 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,111,916 · 10 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
1w02w05w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x1c389468…6b0e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2dc6d66e…08f6
0x065c9d…c394
2 touches
0 conflicts
0x3a347a58…95e1
0x065c9d…c394
2 touches
0 conflicts
0x55f95c5d…28e0
0x065c9d…c394
2 touches
0 conflicts
0x71bab510…23aa
0x065c9d…c394
2 touches
0 conflicts
0xc3d1ad3c…4bb9
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 0xffe431af56…838faa
Audit this contract →
← previous block·next block →recent activity