← previous blocknext block →recent activity
Analyzing
Block #74,331,885
26 transactions · 16 stateful · 2026-05-13 13:45:25 UTC
Parallelism
92/100
Blocked
25%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,331,885 · 26 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
1w03w016w117w123w124w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x3d454d12…caf4
0x065c9d…c394
2 touches
0 conflicts
0x00000000…000b
0x10da0c…e102
2 touches
0 conflicts
0x765c236f…ff45
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…000b
0x5d823e…89c6
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 0x5c8c6ab6f0…86dc36
Audit this contract →
← previous block·next block →recent activity