← previous blocknext block →recent activity
Analyzing
Block #75,843,386
9 transactions · 9 stateful · 2026-05-20 14:06:18 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,843,386 · 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
1w02w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x683fde84…491b
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2578f3dc…b3d7
0x2a68ba…90c5
4 touches
1 conflict
0xd934eb52…a159
0x065c9d…c394
3 touches
1 conflict
0x058ec6a4…4c5a
0x065c9d…c394
3 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
2 touches
0 conflicts
0x95d630b0…0180
0x34b655…2a6f
2 touches
0 conflicts
0xa176d22f…9aa8
0x34b655…2a6f
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 0x683fde8468…62491b
Audit this contract →
← previous block·next block →recent activity