← previous blocknext block →recent activity
Analyzing
Block #106,367,183
26 transactions · 24 stateful · 2026-09-20 04:25:01 UTC
Parallelism
62/100
Blocked
71%
Avg conflicts / tx
2.38
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,367,183 · 26 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w17w28w39w410w511w117w418w619w720w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89eaf36a…4e48
0x34b655…2a6f
14 touches
21 conflicts
0x87c1cd94…e6df
0x34b655…2a6f
12 touches
15 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0xdd77da90…6df4
0x34b655…2a6f
10 touches
10 conflicts
0x74e46435…fdcd
0x34b655…2a6f
10 touches
10 conflicts
0xf58eca50…59f8
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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 0x89eaf36ae4…6e4e48
Audit this contract →
← previous block·next block →recent activity