← previous blocknext block →recent activity
Analyzing
Block #73,210,018
11 transactions · 9 stateful · 2026-05-08 09:02:01 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,210,018 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18ca3690…0c6f
0x065c9d…c394
4 touches
1 conflict
0xce7bfe5e…5e58
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x71902533…2b06
0x065c9d…c394
3 touches
1 conflict
0x2f7fc450…03d5
0x065c9d…c394
3 touches
1 conflict
0x200e1edd…bc96
0x065c9d…c394
2 touches
0 conflicts
0x4b5f1115…405e
0x065c9d…c394
2 touches
0 conflicts
0x978a1f72…2475
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 0x18ca3690bb…010c6f
Audit this contract →
← previous block·next block →recent activity