← previous blocknext block →recent activity
Analyzing
Block #73,654,193
20 transactions · 19 stateful · 2026-05-10 10:19:25 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
1.2
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,654,193 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w08w19w210w111w212w313w414w515w618w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
10 touches
10 conflicts
0x0ac31945…2c72
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xb91a6f59…722c
0x34b655…2a6f
4 touches
1 conflict
0x0355299f…afa3
0x065c9d…c394
3 touches
1 conflict
0x05854468…165c
0x065c9d…c394
3 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
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: MarginAccount
10 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity