← previous blocknext block →recent activity
Analyzing
Block #73,696,902
31 transactions · 24 stateful · 2026-05-10 15:07:32 UTC
Parallelism
65/100
Blocked
63%
Avg conflicts / tx
2.06
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #73,696,902 · 31 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w012w113w218w219w220w321w422w323w424w525w626w727w828w929w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
16 touches
28 conflicts
0x0ac31945…2c72
0x065c9d…c394
14 touches
21 conflicts
0x046a928e…0012
0x2a68ba…90c5
12 touches
15 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
12 touches
15 conflicts
0x529acb6a…fcc6
0x065c9d…c394
10 touches
10 conflicts
0x2234696e…3f95
0x065c9d…c394
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x6fbf2195…8660
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
28 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity