← previous blocknext block →recent activity
Analyzing
Block #105,933,105
27 transactions · 25 stateful · 2026-09-18 16:00:13 UTC
Parallelism
81/100
Blocked
32%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,933,105 · 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
2w03w14w15w06w17w28w110w011w113w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b458e47…5ab5
0x34b655…2a6f
8 touches
6 conflicts
0xa5ab7b8a…c97b
0x34b655…2a6f
6 touches
3 conflicts
0x5d78c41c…00b5
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xb548e15e…381e
0x34b655…2a6f
6 touches
3 conflicts
0x8d47c9a4…f11b
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x737acb78…fce8
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
6 conflicts on slot 0x1b458e4770…d25ab5
Audit this contract →
← previous block·next block →recent activity