← previous blocknext block →recent activity
Analyzing
Block #75,333,303
11 transactions · 8 stateful · 2026-05-18 05:14:55 UTC
Parallelism
82/100
Blocked
25%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,333,303 · 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
1w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa363a0da…0ed3
0x065c9d…c394
4 touches
1 conflict
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0x1c44494e…1351
0x065c9d…c394
3 touches
1 conflict
0x67c7b4dc…7fd9
0x065c9d…c394
3 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
2 touches
0 conflicts
0xbb013f31…f1ad
0x065c9d…c394
2 touches
0 conflicts
0xbe7dd2f3…cb2a
0x065c9d…c394
2 touches
0 conflicts
0xc63061b3…b309
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 0xa363a0da9b…360ed3
Audit this contract →
← previous block·next block →recent activity