← previous blocknext block →recent activity
Analyzing
Block #106,565,403
25 transactions · 24 stateful · 2026-09-20 21:02:40 UTC
Parallelism
76/100
Blocked
50%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,565,403 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w18w09w112w214w216w317w418w520w321w423w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7849366c…8914
0x34b655…2a6f
8 touches
6 conflicts
0xf820a074…e5b6
0x34b655…2a6f
8 touches
6 conflicts
0x4be9812b…48a9
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x16a8cd0c…27bd
0x34b655…2a6f
4 touches
1 conflict
0x7d6b9af1…9a38
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
6 conflicts on slot 0x7849366c03…548914
Audit this contract →
← previous block·next block →recent activity