← previous blocknext block →recent activity
Analyzing
Block #105,841,486
18 transactions · 17 stateful · 2026-09-18 08:18:05 UTC
Parallelism
61/100
Blocked
53%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,841,486 · 18 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
1w05w06w18w29w310w411w512w613w014w116w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7ce83b1…2c96
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xe40012e6…121d
0x34b655…2a6f
10 touches
10 conflicts
0xe2def47d…8105
0x34b655…2a6f
10 touches
10 conflicts
0x7b67f6cf…0aab
0x34b655…2a6f
8 touches
6 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x1470cae0…177e
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xb7ce83b1b6…352c96
Audit this contract →
← previous block·next block →recent activity