← previous blocknext block →recent activity
Analyzing
Block #106,366,789
16 transactions · 15 stateful · 2026-09-20 04:23:02 UTC
Parallelism
56/100
Blocked
60%
Avg conflicts / tx
2.06
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,366,789 · 16 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
1w02w13w14w15w27w29w310w411w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85ac8cc2…3104
0x34b655…2a6f
14 touches
21 conflicts
0xb1927b58…f161
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x2c2761c0…476e
0x34b655…2a6f
8 touches
6 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
6 touches
3 conflicts
0x000bde1a…e123
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x1b25f260…c429
0x34b655…2a6f
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
21 conflicts on slot 0x85ac8cc23d…013104
Audit this contract →
← previous block·next block →recent activity