← previous blocknext block →recent activity
Analyzing
Block #74,750,788
10 transactions · 9 stateful · 2026-05-15 12:23:10 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,750,788 · 10 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
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x1a60288a…67c8
0x065c9d…c394
2 touches
0 conflicts
0x8db7c9a7…c053
0x065c9d…c394
2 touches
0 conflicts
0xafd5f258…5673
0x065c9d…c394
2 touches
0 conflicts
0xb48e72d7…3bc1
0x065c9d…c394
2 touches
0 conflicts
0xda999651…fd4d
0x065c9d…c394
2 touches
0 conflicts
0xe04520f2…b355
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity