← previous blocknext block →recent activity
Analyzing
Block #75,518,373
14 transactions · 6 stateful · 2026-05-19 01:58:21 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,518,373 · 14 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0bc9929…84a3
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xba17041c…11ea
0x065c9d…c394
3 touches
1 conflict
0x8355fb0b…8526
0x065c9d…c394
2 touches
0 conflicts
0xa4053ea0…5767
0x065c9d…c394
2 touches
0 conflicts
0xb962f7c1…0d8a
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x1d1325…2305
2 touches
0 conflicts
0xa17ec269…7cdd
0x1d1325…2305
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 0xf0bc99299f…2084a3
Audit this contract →
← previous block·next block →recent activity