← previous blocknext block →recent activity
Analyzing
Block #105,932,637
19 transactions · 18 stateful · 2026-09-18 15:57:52 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
1.26
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,932,637 · 19 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
1w02w13w24w35w46w07w012w113w217w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x1b458e47…5ab5
0x34b655…2a6f
10 touches
10 conflicts
0xc4bbc89f…fca8
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xc102b2b7…57a2
0x34b655…2a6f
8 touches
6 conflicts
0xb8dc136f…fb16
0xc8689a…ee79
8 touches
6 conflicts
0x31519d10…f76b
0x34b655…2a6f
8 touches
6 conflicts
0x3d6c26e5…1b45
0x34b655…2a6f
8 touches
6 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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity