← previous blocknext block →recent activity
Analyzing
Block #106,944,264
30 transactions · 28 stateful · 2026-09-22 04:50:32 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.9
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,944,264 · 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
1w02w13w24w35w410w411w514w615w717w422w823w924w1029w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60dcfcd4…a1d2
0x34b655…2a6f
18 touches
36 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
14 touches
21 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…002d
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0xea2d3331…6e36
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
36 conflicts on slot 0x60dcfcd423…0aa1d2
Audit this contract →
← previous block·next block →recent activity