← previous blocknext block →recent activity
Analyzing
Block #74,643,388
11 transactions · 9 stateful · 2026-05-15 00:26:35 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,643,388 · 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
1w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x487594a4…6c46
0x065c9d…c394
4 touches
1 conflict
0xab379b4e…a17b
0x065c9d…c394
3 touches
1 conflict
0xaadaaa2e…a90e
0x065c9d…c394
3 touches
1 conflict
0xe68e32b2…4a52
0x065c9d…c394
3 touches
1 conflict
0x2456075e…d084
0x065c9d…c394
2 touches
0 conflicts
0x502abd89…1251
0x065c9d…c394
2 touches
0 conflicts
0xc89f4508…e47c
0x065c9d…c394
2 touches
0 conflicts
0xd68cb7b6…e84e
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 0x487594a4da…756c46
Audit this contract →
← previous block·next block →recent activity