← previous blocknext block →recent activity
Analyzing
Block #106,392,677
30 transactions · 29 stateful · 2026-09-20 06:33:20 UTC
Parallelism
63/100
Blocked
66%
Avg conflicts / tx
2.4
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,392,677 · 30 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w18w211w313w316w417w520w622w723w824w925w1029w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89eaf36a…4e48
0x34b655…2a6f
18 touches
36 conflicts
0xaa71850b…95ea
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001a
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002a
0x1b6862…e19c
12 touches
15 conflicts
0x3bd55803…5d4a
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 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
36 conflicts on slot 0x89eaf36ae4…6e4e48
Audit this contract →
← previous block·next block →recent activity