← previous blocknext block →recent activity
Analyzing
Block #105,931,107
19 transactions · 18 stateful · 2026-09-18 15:50:10 UTC
Parallelism
63/100
Blocked
67%
Avg conflicts / tx
1.58
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,931,107 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w19w210w311w412w513w615w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe796f8b7…ad55
0x34b655…2a6f
10 touches
10 conflicts
0x3ee13af7…3ccc
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0019
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 conflicts
0x58e06bab…34cc
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
10 conflicts on slot 0xe796f8b7af…c7ad55
Audit this contract →
← previous block·next block →recent activity