← previous blocknext block →recent activity
Analyzing
Block #73,674,189
30 transactions · 24 stateful · 2026-05-10 12:34:20 UTC
Parallelism
83/100
Blocked
54%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,674,189 · 30 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
1w02w14w05w18w210w111w214w015w118w019w121w222w323w425w226w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xfe3b32e1…0571
0xd32edf…ff58
9 touches
10 conflicts
0x529acb6a…fcc6
0x065c9d…c394
8 touches
6 conflicts
0x0ac31945…2c72
0x065c9d…c394
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x73db7d26…87c3
0x065c9d…c394
4 touches
3 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
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