← previous blocknext block →recent activity
Analyzing
Block #74,312,776
13 transactions · 9 stateful · 2026-05-13 11:38:24 UTC
Parallelism
85/100
Blocked
22%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,312,776 · 13 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
1w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24968e6d…0132
0x065c9d…c394
4 touches
1 conflict
0xbbee74c2…567a
0x065c9d…c394
4 touches
1 conflict
0x8d781551…f38d
0x065c9d…c394
3 touches
1 conflict
0x91f7ef79…6d7d
0x065c9d…c394
3 touches
1 conflict
0x4712798f…f6ec
0x065c9d…c394
2 touches
0 conflicts
0xa3f2b14d…b189
0x065c9d…c394
2 touches
0 conflicts
0xf25b5102…c100
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0x24968e6db4…f00132
Audit this contract →
← previous block·next block →recent activity