← previous blocknext block →recent activity
Analyzing
Block #106,198,563
19 transactions · 19 stateful · 2026-09-19 14:16:21 UTC
Parallelism
79/100
Blocked
47%
Avg conflicts / tx
0.89
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,198,563 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w010w111w112w013w114w215w318w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x78f38373…89fb
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0x73894a77…8136
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0x10c19272…7445
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
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
6 conflicts on slot 0x78f3837317…2289fb
Audit this contract →
← previous block·next block →recent activity