← previous blocknext block →recent activity
Analyzing
Block #105,749,743
27 transactions · 25 stateful · 2026-09-18 00:35:03 UTC
Parallelism
78/100
Blocked
48%
Avg conflicts / tx
1.15
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,749,743 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w08w19w212w321w223w424w525w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ca7cd2f…e030
0x34b655…2a6f
10 touches
10 conflicts
0xdb69fcd0…9c87
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c4
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 0x1ca7cd2f09…8ce030
Audit this contract →
← previous block·next block →recent activity