← previous blocknext block →recent activity
Analyzing
Block #105,575,347
19 transactions · 19 stateful · 2026-09-17 09:57:14 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,575,347 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w08w49w510w615w618w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf496f80c…d5c8
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xb3d671ff…a53b
0x34b655…2a6f
8 touches
6 conflicts
0x6c0e32fc…a6ca
0x34b655…2a6f
6 touches
3 conflicts
0xd5c98027…9fd9
0x34b655…2a6f
6 touches
3 conflicts
0x59dccbd8…2bf6
0x34b655…2a6f
4 touches
1 conflict
0x8d6980af…d4ce
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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 0xf496f80c95…3ed5c8
Audit this contract →
← previous block·next block →recent activity