← previous blocknext block →recent activity
Analyzing
Block #102,810,200
31 transactions · 30 stateful · 2026-09-07 17:14:22 UTC
Parallelism
71/100
Blocked
63%
Avg conflicts / tx
1.26
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #102,810,200 · 31 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
1w02w13w24w35w48w110w114w215w316w417w518w619w720w821w428w329w430w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce105feb…f8ff
0x40c49f…2af0
12 touches
15 conflicts
0x6518075e…2b17
0x2a68ba…90c5
11 touches
15 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x5086c64a…28ba
0x34b655…2a6f
8 touches
6 conflicts
0x15698ac9…2a46
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
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 0xce105febd1…3af8ff
Audit this contract →
← previous block·next block →recent activity