← previous blocknext block →recent activity
Analyzing
Block #106,200,474
29 transactions · 27 stateful · 2026-09-19 14:25:58 UTC
Parallelism
72/100
Blocked
63%
Avg conflicts / tx
1.72
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,200,474 · 29 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w18w29w310w411w512w613w721w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98568c43…ff4e
0x34b655…2a6f
16 touches
28 conflicts
0x23a320fb…cbd7
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xec85b41e…7c96
0x1b6862…e19c
8 touches
6 conflicts
0x1b25f260…c429
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
28 conflicts on slot 0x98568c43d7…70ff4e
Audit this contract →
← previous block·next block →recent activity