← previous blocknext block →recent activity
Analyzing
Block #74,241,208
10 transactions · 9 stateful · 2026-05-13 03:42:22 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,241,208 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf823e97f…2ee6
0x065c9d…c394
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x0bf94883…0ae7
0x065c9d…c394
2 touches
0 conflicts
0xcf3283ba…c9fa
0x065c9d…c394
2 touches
0 conflicts
0xe3fc4221…f2f9
0x065c9d…c394
2 touches
0 conflicts
0xec095e0f…e072
0x065c9d…c394
2 touches
0 conflicts
0x00000000…009a
0x16f70c…c3dd
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
6 conflicts on slot 0xf823e97fa0…262ee6
Audit this contract →
← previous block·next block →recent activity