← previous blocknext block →recent activity
Analyzing
Block #106,395,398
30 transactions · 26 stateful · 2026-09-20 06:47:01 UTC
Parallelism
83/100
Blocked
58%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,395,398 · 30 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w18w09w010w113w114w215w316w218w321w423w224w328w329w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc78b8610…8ca1
0x34b655…2a6f
8 touches
6 conflicts
0x1fe265c5…efd6
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xf35dca9e…bd8a
0x1b6862…e19c
6 touches
3 conflicts
0x02fa927d…6468
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xc78b8610f4…cd8ca1
Audit this contract →
← previous block·next block →recent activity