← previous blocknext block →recent activity
Analyzing
Block #105,932,716
22 transactions · 20 stateful · 2026-09-18 15:58:15 UTC
Parallelism
82/100
Blocked
35%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,932,716 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w313w114w215w319w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a429191…9cda
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x31519d10…f76b
0x34b655…2a6f
6 touches
3 conflicts
0x3180cd66…aaef
0x34b655…2a6f
6 touches
3 conflicts
0x3d6c26e5…1b45
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x708d7a74…09e3
0x34b655…2a6f
6 touches
3 conflicts
0x9ff4ca89…6115
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
6 conflicts on slot 0x3a42919159…6b9cda
Audit this contract →
← previous block·next block →recent activity