← previous blocknext block →recent activity
Analyzing
Block #105,643,672
33 transactions · 31 stateful · 2026-09-17 15:41:11 UTC
Parallelism
85/100
Blocked
32%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,643,672 · 33 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
1w02w14w05w16w07w18w113w014w116w218w319w429w030w132w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x503ed4b3…7333
0x34b655…2a6f
8 touches
6 conflicts
0xbdb7aec1…c95b
0x34b655…2a6f
8 touches
6 conflicts
0x6771eae2…7014
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe3684e08…c96a
0x34b655…2a6f
6 touches
3 conflicts
0xe8f5e33f…719c
0x34b655…2a6f
6 touches
3 conflicts
0xd5b10148…e634
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
6 conflicts on slot 0x503ed4b3d1…f47333
Audit this contract →
← previous block·next block →recent activity