← previous blocknext block →recent activity
Analyzing
Block #102,809,602
30 transactions · 25 stateful · 2026-09-07 17:11:19 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.8
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,809,602 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w113w014w215w316w417w518w619w120w127w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
14 touches
21 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x64bc8c0c…f3cf
0x40c49f…2af0
8 touches
6 conflicts
0x3597104f…cf32
0x34b655…2a6f
4 touches
1 conflict
0x27754bd4…96ae
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
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: MarginAccount
21 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity