← previous blocknext block →recent activity
Analyzing
Block #106,464,341
20 transactions · 20 stateful · 2026-09-20 12:34:03 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.2
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,464,341 · 20 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
1w02w13w24w35w08w19w111w012w213w314w415w519w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x228da3f5…c2bf
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xdb95e18e…c73b
0x1b6862…e19c
8 touches
6 conflicts
0x2aab0897…78f7
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
15 conflicts on slot 0x228da3f59c…57c2bf
Audit this contract →
← previous block·next block →recent activity