← previous blocknext block →recent activity
Analyzing
Block #103,050,183
21 transactions · 21 stateful · 2026-09-08 13:22:40 UTC
Parallelism
71/100
Blocked
57%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #103,050,183 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w16w37w18w211w414w515w116w519w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ae9195f…9cb7
0x34b655…2a6f
12 touches
15 conflicts
0x55192654…91fe
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x937a52a8…2719
0x34b655…2a6f
8 touches
6 conflicts
0x25180879…8191
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
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: Perpl
15 conflicts on slot 0x1ae9195f63…e69cb7
Audit this contract →
← previous block·next block →recent activity