← previous blocknext block →recent activity
Analyzing
Block #75,015,777
12 transactions · 8 stateful · 2026-05-16 17:54:08 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,015,777 · 12 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
2w05w16w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe2e9fdb…90e2
0x065c9d…c394
4 touches
1 conflict
0xda5d7fe6…5574
0x065c9d…c394
4 touches
1 conflict
0xbd039566…f039
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb70188c2…24d9
0x065c9d…c394
4 touches
1 conflict
0x34987bc5…71c7
0x065c9d…c394
3 touches
1 conflict
0xb6881cdf…a7df
0x065c9d…c394
3 touches
1 conflict
0xea8aeba3…4531
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 0xfe2e9fdbf8…dd90e2
Audit this contract →
← previous block·next block →recent activity