← previous blocknext block →recent activity
Analyzing
Block #102,817,217
30 transactions · 29 stateful · 2026-09-07 17:49:44 UTC
Parallelism
70/100
Blocked
66%
Avg conflicts / tx
1.4
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #102,817,217 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w18w310w214w315w416w417w518w619w720w821w128w429w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab374ce7…e368
0x40c49f…2af0
12 touches
15 conflicts
0x002fed35…79fa
0x2a68ba…90c5
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd8f2a8a6…c9fa
0xd32edf…ff58
7 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 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: 0x40c49f17…d22af0
15 conflicts on slot 0xab374ce76e…a7e368
Audit this contract →
← previous block·next block →recent activity