← previous blocknext block →recent activity
Analyzing
Block #75,107,141
13 transactions · 13 stateful · 2026-05-17 04:03:24 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,107,141 · 13 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
1w02w14w08w19w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0x08943ea2…ed03
0x754704…b603
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0xab18385f…55bb
0xd32edf…ff58
3 touches
1 conflict
0x115f40da…1709
0x065c9d…c394
3 touches
1 conflict
0x8cef77ee…fb67
0x065c9d…c394
3 touches
1 conflict
0xb260335f…3b3d
0x065c9d…c394
3 touches
1 conflict
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 0x348fda08cf…fc7e96
Audit this contract →
← previous block·next block →recent activity