← previous blocknext block →recent activity
Analyzing
Block #106,215,896
35 transactions · 30 stateful · 2026-09-19 15:43:38 UTC
Parallelism
69/100
Blocked
70%
Avg conflicts / tx
2.14
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,215,896 · 35 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w38w414w516w617w718w819w521w922w1023w1032w233w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7af7ea3…7d7d
0x34b655…2a6f
18 touches
36 conflicts
0xb5e11716…1afb
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001f
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
10 touches
10 conflicts
0x3bd55803…5d4f
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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
36 conflicts on slot 0xb7af7ea38f…ad7d7d
Audit this contract →
← previous block·next block →recent activity