← previous blocknext block →recent activity
Analyzing
Block #103,049,842
27 transactions · 27 stateful · 2026-09-08 13:20:57 UTC
Parallelism
81/100
Blocked
48%
Avg conflicts / tx
1.07
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #103,049,842 · 27 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
1w04w05w06w17w28w39w410w112w115w216w318w219w321w126w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xac389ba9…8b45
0x34b655…2a6f
6 touches
3 conflicts
0x05ab500a…6177
0x34b655…2a6f
6 touches
3 conflicts
0x915c095e…c1e5
0x34ae4d…3fc5
4 touches
1 conflict
0xcfe06a18…b5b5
0x34ae4d…3fc5
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity