← previous blocknext block →recent activity
Analyzing
Block #75,141,015
9 transactions · 8 stateful · 2026-05-17 07:49:25 UTC
Parallelism
78/100
Blocked
25%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,141,015 · 9 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
1w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ad47a93…fdbc
0x065c9d…c394
4 touches
1 conflict
0x0b934a05…024a
0x065c9d…c394
4 touches
1 conflict
0x7dfa80bd…6ba1
0x065c9d…c394
3 touches
1 conflict
0x9380bd95…265e
0x065c9d…c394
3 touches
1 conflict
0xc865a242…da33
0x065c9d…c394
3 touches
1 conflict
0x224847a0…b8e9
0x065c9d…c394
3 touches
1 conflict
0x60d04ff7…6096
0x065c9d…c394
2 touches
0 conflicts
0xe0fb2c61…4357
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 0x5ad47a9342…8efdbc
Audit this contract →
← previous block·next block →recent activity