← previous blocknext block →recent activity
Analyzing
Block #105,643,663
33 transactions · 31 stateful · 2026-09-17 15:41:09 UTC
Parallelism
73/100
Blocked
61%
Avg conflicts / tx
1.82
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #105,643,663 · 33 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w07w18w29w210w313w314w419w521w422w523w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x503ed4b3…7333
0x34b655…2a6f
16 touches
28 conflicts
0xe3684e08…c96a
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x38bcfe5f…6c71
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0xe8f5e33f…719c
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0x503ed4b3d1…f47333
Audit this contract →
← previous block·next block →recent activity