← previous blocknext block →recent activity
Analyzing
Block #106,535,085
21 transactions · 21 stateful · 2026-09-20 18:30:05 UTC
Parallelism
67/100
Blocked
48%
Avg conflicts / tx
0.71
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,535,085 · 21 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
1w02w13w24w35w47w08w010w415w116w217w518w120w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70f57071…47ca
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0fc536fb…1aa1
0x34b655…2a6f
6 touches
3 conflicts
0x028892a4…90ac
0x34b655…2a6f
6 touches
3 conflicts
0x10b1245e…de66
0x34b655…2a6f
4 touches
1 conflict
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x69411fb3…e36d
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x70f570719e…4647ca
Audit this contract →
← previous block·next block →recent activity