← previous blocknext block →recent activity
Analyzing
Block #74,270,817
9 transactions · 7 stateful · 2026-05-13 06:59:11 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,270,817 · 9 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
1w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf1728d97…8d64
0x065c9d…c394
3 touches
1 conflict
0xdf9f745e…f340
0x065c9d…c394
3 touches
1 conflict
0x1c885db3…68f1
0x065c9d…c394
2 touches
0 conflicts
0x24968e6d…0132
0x065c9d…c394
2 touches
0 conflicts
0x354663aa…de94
0x065c9d…c394
2 touches
0 conflicts
0x40dff612…7f61
0x065c9d…c394
2 touches
0 conflicts
0x67a3629c…0199
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