← previous blocknext block →recent activity
Analyzing
Block #102,493,399
146 transactions · 85 stateful · 2026-09-06 14:32:18 UTC
Parallelism
84/100
Blocked
79%
Avg conflicts / tx
2.06
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #102,493,399 · 146 txs across 24 waves · depth 24
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
wave w21
wave w22
wave w23
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w27w38w49w510w611w712w813w961w1063w1167w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
26 touches
78 conflicts
0x8284ccf9…1dcc
0xd32edf…ff58
25 touches
78 conflicts
0x00000000…003d
0xa6afd3…d132
16 touches
28 conflicts
0x17606ba6…1b6e
0x754704…b603
16 touches
28 conflicts
0x00000000…002c
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0xf2e7bb96…1a57
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 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
78 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity