← previous blocknext block →recent activity
Analyzing
Block #75,032,469
10 transactions · 8 stateful · 2026-05-16 19:45:18 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,032,469 · 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
2w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f82f72d…0e7e
0x065c9d…c394
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x0ff08152…06c7
0x065c9d…c394
3 touches
1 conflict
0x09e407c2…1a5b
0x065c9d…c394
3 touches
1 conflict
0x52f1465d…abfc
0x065c9d…c394
2 touches
0 conflicts
0xaa12290e…a193
0x065c9d…c394
2 touches
0 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
2 touches
0 conflicts
0x765c236f…ff45
0x2a68ba…90c5
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 0x6f82f72d74…370e7e
Audit this contract →
← previous block·next block →recent activity