← previous blocknext block →recent activity
Analyzing
Block #102,042,670
78 transactions · 72 stateful · 2026-09-05 00:28:04 UTC
Parallelism
87/100
Blocked
65%
Avg conflicts / tx
2.33
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #102,042,670 · 78 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w28w010w111w012w113w214w315w416w517w625w328w651w858w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
18 touches
36 conflicts
0x00000000…0002
0xf5b5f7…6d70
18 touches
36 conflicts
0x130b33bc…2079
0xd32edf…ff58
17 touches
36 conflicts
0x77ed432f…fa04
0x065c9d…c394
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
14 touches
21 conflicts
0x1b60b708…5b4b
0x34ae4d…3fc5
12 touches
15 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
36 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity