← previous blocknext block →recent activity
Analyzing
Block #76,108,467
12 transactions · 8 stateful · 2026-05-21 19:32:46 UTC
Parallelism
83/100
Blocked
13%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,108,467 · 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
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x03d8353a…75c9
0x065c9d…c394
2 touches
0 conflicts
0x1c63e8e4…056a
0x065c9d…c394
2 touches
0 conflicts
0x47b807a2…3307
0x065c9d…c394
2 touches
0 conflicts
0x8466f92a…7079
0x065c9d…c394
2 touches
0 conflicts
0x8a1da972…5271
0x065c9d…c394
2 touches
0 conflicts
0xed4aec2d…c088
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