← previous blocknext block →recent activity
Analyzing
Block #106,380,462
27 transactions · 25 stateful · 2026-09-20 05:31:51 UTC
Parallelism
70/100
Blocked
60%
Avg conflicts / tx
1.63
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,380,462 · 27 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w19w211w312w414w317w218w519w320w421w522w625w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x564e36eb…6d6a
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xc8cb0701…3926
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0xd4c913d7…343a
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
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
15 conflicts on slot 0x564e36eb6b…a96d6a
Audit this contract →
← previous block·next block →recent activity