← previous blocknext block →recent activity
Analyzing
Block #102,656,276
10 transactions · 9 stateful · 2026-09-07 04:16:50 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,656,276 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ce66ac3…cfa3
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5e3014f0…b4e1
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xec899474…0c96
0x188d58…ea8e
2 touches
0 conflicts
0x0c03b662…be24
0x27bc99…9a93
2 touches
0 conflicts
0x3f1aa9d2…c0aa
0x27bc99…9a93
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 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: Perpl
1 conflict on slot 0x0ce66ac3b0…16cfa3
Audit this contract →
← previous block·next block →recent activity