← previous blocknext block →recent activity
Analyzing
Block #73,753,428
19 transactions · 19 stateful · 2026-05-10 21:29:02 UTC
Parallelism
74/100
Blocked
32%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,753,428 · 19 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
2w04w19w211w012w113w314w417w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x7f81fb82…633e
0x065c9d…c394
8 touches
6 conflicts
0x44ad89ba…cf83
0x5e1b1a…7777
4 touches
1 conflict
0x4d1acd7c…f345
0x5e1b1a…7777
4 touches
1 conflict
0x00000000…0000
0x75c3ab…4f0d
4 touches
1 conflict
0x00000000…0001
0x75c3ab…4f0d
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x8a2657f5…e008
0x34b655…2a6f
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity