← previous blocknext block →recent activity
Analyzing
Block #106,565,370
31 transactions · 22 stateful · 2026-09-20 21:02:30 UTC
Parallelism
84/100
Blocked
41%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,565,370 · 31 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
9w012w113w215w016w118w119w221w225w126w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4089d428…b018
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0xab2a87f1…eb01
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 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
3 conflicts on slot 0x4089d42830…afb018
Audit this contract →
← previous block·next block →recent activity