← previous blocknext block →recent activity
Analyzing
Block #74,311,159
8 transactions · 8 stateful · 2026-05-13 11:27:37 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,311,159 · 8 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbbee74c2…567a
0x065c9d…c394
4 touches
1 conflict
0x24968e6d…0132
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4ad4589b…27b8
0x065c9d…c394
2 touches
0 conflicts
0x4ebf1f2d…379a
0x065c9d…c394
2 touches
0 conflicts
0x570a189b…0b1c
0x065c9d…c394
2 touches
0 conflicts
0x5a23814e…b484
0x065c9d…c394
2 touches
0 conflicts
0x5c8c6ab6…dc36
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 0xbbee74c2e7…6e567a
Audit this contract →
← previous block·next block →recent activity