← previous blocknext block →recent activity
Analyzing
Block #75,301,313
13 transactions · 11 stateful · 2026-05-18 01:40:51 UTC
Parallelism
85/100
Blocked
18%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,301,313 · 13 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
2w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd118d39f…f6a2
0x065c9d…c394
4 touches
1 conflict
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0x42b52279…1436
0x065c9d…c394
3 touches
1 conflict
0x10d0fa74…937d
0x065c9d…c394
3 touches
1 conflict
0x1130c6bc…7a18
0x065c9d…c394
2 touches
0 conflicts
0x443a3e47…f4a4
0x065c9d…c394
2 touches
0 conflicts
0x4b820498…d1d4
0x065c9d…c394
2 touches
0 conflicts
0x4faf46b3…7516
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 0xd118d39f5b…1af6a2
Audit this contract →
← previous block·next block →recent activity