← previous blocknext block →recent activity
Analyzing
Block #105,856,766
22 transactions · 20 stateful · 2026-09-18 09:35:07 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
1.36
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,856,766 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w011w112w213w314w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x97e4c862…4419
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x8ff3b648…a05a
0x34b655…2a6f
8 touches
6 conflicts
0xb3aa2022…9e09
0x34b655…2a6f
6 touches
3 conflicts
0xdca71fea…cf39
0x34b655…2a6f
6 touches
3 conflicts
0x77582823…fe8e
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity