← previous blocknext block →recent activity
Analyzing
Block #106,467,403
17 transactions · 15 stateful · 2026-09-20 12:49:27 UTC
Parallelism
59/100
Blocked
53%
Avg conflicts / tx
1.24
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,467,403 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w410w011w112w215w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd4e632c…e14c
0x34b655…2a6f
10 touches
10 conflicts
0x22659874…ec0b
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
8 touches
6 conflicts
0xb7e8b0c4…dec3
0x34b655…2a6f
8 touches
6 conflicts
0xbd3735d7…c973
0x34b655…2a6f
8 touches
6 conflicts
0xc04a9203…7d63
0x34b655…2a6f
8 touches
6 conflicts
0xc20996bb…30e0
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 0xfd4e632c76…e1e14c
Audit this contract →
← previous block·next block →recent activity