← previous blocknext block →recent activity
Analyzing
Block #74,900,492
16 transactions · 13 stateful · 2026-05-16 05:02:37 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,900,492 · 16 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
1w07w19w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe18822b5…8e43
0x065c9d…c394
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9bb66190…58d9
0x065c9d…c394
4 touches
1 conflict
0xdce6bdde…afdb
0x065c9d…c394
3 touches
1 conflict
0x4deddd83…d1f3
0x065c9d…c394
3 touches
1 conflict
0xec3e68da…1fe6
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 0xe18822b5af…768e43
Audit this contract →
← previous block·next block →recent activity