← previous blocknext block →recent activity
Analyzing
Block #106,946,800
22 transactions · 21 stateful · 2026-09-22 05:03:18 UTC
Parallelism
73/100
Blocked
62%
Avg conflicts / tx
1.41
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,946,800 · 22 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
2w03w14w25w27w39w310w111w012w114w215w118w419w521w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01ad5dd0…11a1
0x34b655…2a6f
10 touches
10 conflicts
0x9d3e71c7…3a5e
0x34b655…2a6f
10 touches
10 conflicts
0x8833a938…05be
0xd32edf…ff58
9 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
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
10 conflicts on slot 0x01ad5dd035…5d11a1
Audit this contract →
← previous block·next block →recent activity