← previous blocknext block →recent activity
Analyzing
Block #105,851,917
36 transactions · 33 stateful · 2026-09-18 09:10:43 UTC
Parallelism
61/100
Blocked
55%
Avg conflicts / tx
1.81
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #105,851,917 · 36 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w08w012w014w118w119w220w221w322w423w124w227w528w629w730w831w932w1033w1134w1235w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0xb5cddf91…0abf
0x34b655…2a6f
8 touches
6 conflicts
0x7aad02c6…b979
0x34b655…2a6f
8 touches
6 conflicts
0x5d35ecc8…a57f
0x34b655…2a6f
8 touches
6 conflicts
0x382434ca…96b5
0x34b655…2a6f
8 touches
6 conflicts
0xec63e4f6…4778
0x34b655…2a6f
7 touches
6 conflicts
0xf1b3debb…7432
0x34b655…2a6f
6 touches
3 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
45 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity