← previous blocknext block →recent activity
Analyzing
Block #106,027,166
29 transactions · 21 stateful · 2026-09-18 23:53:47 UTC
Parallelism
62/100
Blocked
57%
Avg conflicts / tx
1.72
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,027,166 · 29 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w28w310w412w514w616w721w224w326w827w928w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
16 touches
28 conflicts
0xbc8fb280…76a3
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
12 touches
15 conflicts
0x48828733…fd48
0x34b655…2a6f
10 touches
10 conflicts
0x48b6f2c7…2ef7
0x34b655…2a6f
10 touches
10 conflicts
0x69d2053b…935a
0x34b655…2a6f
10 touches
10 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
10 touches
10 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 0xe1c4e5ce15…770dec
Audit this contract →
← previous block·next block →recent activity