← previous blocknext block →recent activity
Analyzing
Block #102,058,568
152 transactions · 84 stateful · 2026-09-05 01:48:35 UTC
Parallelism
84/100
Blocked
77%
Avg conflicts / tx
3.28
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #102,058,568 · 152 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
1w02w13w24w35w46w57w68w79w825w933w1535w1642w1743w1892w2097w21108w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
36 touches
153 conflicts
0xb0e84767…5c49
0xd32edf…ff58
31 touches
120 conflicts
0x00000000…0015
0x1b6862…e19c
26 touches
78 conflicts
0x00000000…001c
0x1b6862…e19c
26 touches
78 conflicts
0x00000000…002c
0x1b6862…e19c
26 touches
78 conflicts
0x07b5c6c6…8867
0x1b6862…e19c
26 touches
78 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
26 touches
78 conflicts
0x00000000…0012
0x1b6862…e19c
26 touches
78 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
153 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity