← previous blocknext block →recent activity
Analyzing
Block #106,388,339
22 transactions · 21 stateful · 2026-09-20 06:11:30 UTC
Parallelism
68/100
Blocked
57%
Avg conflicts / tx
1.45
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,388,339 · 22 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
1w02w13w24w05w16w17w211w012w115w316w417w518w621w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb3b7a0d…0b58
0x34b655…2a6f
14 touches
21 conflicts
0x9660f3bd…17ce
0x34b655…2a6f
8 touches
6 conflicts
0x038b9243…553d
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x5060cdde…445d
0x34b655…2a6f
8 touches
6 conflicts
0x50c095d8…d0b0
0x34b655…2a6f
8 touches
6 conflicts
0x60a536a6…ef7a
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
21 conflicts on slot 0xeb3b7a0d21…b30b58
Audit this contract →
← previous block·next block →recent activity