← previous blocknext block →recent activity
Analyzing
Block #105,843,782
25 transactions · 24 stateful · 2026-09-18 08:29:45 UTC
Parallelism
76/100
Blocked
63%
Avg conflicts / tx
1.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,843,782 · 25 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
1w02w13w24w35w46w07w18w19w218w219w320w321w422w523w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xf90c6521…d8f0
0x34b655…2a6f
10 touches
10 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
10 touches
10 conflicts
0x6b1259e6…4e14
0x1b6862…e19c
10 touches
10 conflicts
0xdec0a1b0…2fc4
0xd32edf…ff58
9 touches
10 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 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity