← previous blocknext block →recent activity
Analyzing
Block #106,456,858
21 transactions · 18 stateful · 2026-09-20 11:56:23 UTC
Parallelism
52/100
Blocked
72%
Avg conflicts / tx
2.48
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,456,858 · 21 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
1w02w13w24w36w110w211w312w413w414w516w617w718w819w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecc4ac19…b4ac
0x34b655…2a6f
16 touches
28 conflicts
0xcd9ba26b…108d
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001c
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002c
0x1b6862…e19c
10 touches
10 conflicts
0xb0e4f69d…34e5
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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 0xecc4ac19be…8fb4ac
Audit this contract →
← previous block·next block →recent activity