← previous blocknext block →recent activity
Analyzing
Block #106,569,556
30 transactions · 24 stateful · 2026-09-20 21:23:34 UTC
Parallelism
87/100
Blocked
50%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,569,556 · 30 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
1w03w05w06w17w28w39w110w211w012w118w223w124w226w027w128w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x932a9590…0b19
0x34b655…2a6f
8 touches
6 conflicts
0x07bc58c3…e53b
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x20b1228b…2487
0x34b655…2a6f
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x176a426a…091b
0x34b655…2a6f
6 touches
3 conflicts
0xf35dca9e…bd8e
0x1b6862…e19c
4 touches
1 conflict
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 0x932a9590fe…330b19
Audit this contract →
← previous block·next block →recent activity