← previous blocknext block →recent activity
Analyzing
Block #106,435,169
23 transactions · 22 stateful · 2026-09-20 10:07:11 UTC
Parallelism
70/100
Blocked
55%
Avg conflicts / tx
1.7
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,435,169 · 23 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
1w02w07w08w110w111w213w114w215w316w417w518w620w222w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x375df097…cfd4
0x34b655…2a6f
14 touches
21 conflicts
0x8d664414…3344
0x34b655…2a6f
12 touches
15 conflicts
0x3fa1fac4…826c
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x000bde1a…e123
0x34b655…2a6f
8 touches
6 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
8 touches
6 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
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
21 conflicts on slot 0x375df09784…28cfd4
Audit this contract →
← previous block·next block →recent activity