← previous blocknext block →recent activity
Analyzing
Block #102,810,866
30 transactions · 28 stateful · 2026-09-07 17:17:43 UTC
Parallelism
83/100
Blocked
57%
Avg conflicts / tx
1.03
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,810,866 · 30 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w18w210w211w312w413w014w117w018w019w120w221w322w423w124w128w329w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9beac280…c650
0x40c49f…2af0
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0x9b4f173c…94e6
0x34b655…2a6f
8 touches
6 conflicts
0xe2f8c65c…4dfe
0x34b655…2a6f
5 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
10 conflicts on slot 0x9beac28010…fcc650
Audit this contract →
← previous block·next block →recent activity