← previous blocknext block →recent activity
Analyzing
Block #106,917,609
36 transactions · 33 stateful · 2026-09-22 02:36:22 UTC
Parallelism
64/100
Blocked
61%
Avg conflicts / tx
1.61
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,917,609 · 36 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w06w17w08w09w110w211w312w414w215w316w417w518w620w727w129w1230w231w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0463db49…5d05
0x34b655…2a6f
14 touches
21 conflicts
0x69411fb3…e36d
0x34b655…2a6f
14 touches
21 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
10 touches
10 conflicts
0xf71016c7…5c7c
0x34b655…2a6f
10 touches
10 conflicts
0x91685a55…a18b
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x00bd8926…a214
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
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
21 conflicts on slot 0x0463db492b…795d05
Audit this contract →
← previous block·next block →recent activity