← previous blocknext block →recent activity
Analyzing
Block #106,192,990
17 transactions · 16 stateful · 2026-09-19 13:48:18 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,192,990 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w07w112w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfda729a6…3a4e
0x34b655…2a6f
10 touches
10 conflicts
0xac808a27…82db
0x34b655…2a6f
6 touches
3 conflicts
0x81501297…c4b7
0x34b655…2a6f
4 touches
1 conflict
0x9340e06b…1581
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x2b4d664b…95cc
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
10 conflicts on slot 0xfda729a6e6…be3a4e
Audit this contract →
← previous block·next block →recent activity