← previous blocknext block →recent activity
Analyzing
Block #105,928,817
25 transactions · 23 stateful · 2026-09-18 15:38:38 UTC
Parallelism
76/100
Blocked
52%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,928,817 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w05w18w19w110w211w313w014w115w117w118w219w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x678dc413…10a5
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x23b2399c…6e4b
0x34b655…2a6f
10 touches
10 conflicts
0x35b89cd8…5092
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x21d102c4…7f30
0x34b655…2a6f
8 touches
6 conflicts
0x8b52b75c…8a0d
0xa6afd3…d132
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
15 conflicts on slot 0x678dc413b6…4210a5
Audit this contract →
← previous block·next block →recent activity