← previous blocknext block →recent activity
Analyzing
Block #106,235,954
42 transactions · 37 stateful · 2026-09-19 17:24:38 UTC
Parallelism
69/100
Blocked
59%
Avg conflicts / tx
2
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,235,954 · 42 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w06w118w219w320w422w224w528w629w730w831w932w1033w1134w1239w140w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0a4e112…f855
0x34b655…2a6f
18 touches
36 conflicts
0xcac065cd…e05c
0x34b655…2a6f
16 touches
28 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
12 touches
15 conflicts
0xa35509fa…5cb3
0x34b655…2a6f
10 touches
10 conflicts
0xd6d040d9…9ae3
0x34b655…2a6f
8 touches
6 conflicts
0x4d42f16e…a6cd
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x2c2db8e9…fdc7
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
36 conflicts on slot 0xb0a4e112ff…8cf855
Audit this contract →
← previous block·next block →recent activity