← previous blocknext block →recent activity
Analyzing
Block #74,025,626
28 transactions · 24 stateful · 2026-05-12 03:48:22 UTC
Parallelism
82/100
Blocked
54%
Avg conflicts / tx
1.04
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,025,626 · 28 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w18w210w011w112w214w015w117w018w119w220w321w425w127w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001b
0x1b6862…e19c
10 touches
10 conflicts
0xcb45d9d6…cb83
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x76ed954e…05ff
0xd32edf…ff58
9 touches
10 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0004
0x63e48b…53f2
6 touches
3 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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity