← previous blocknext block →recent activity
Analyzing
Block #106,185,413
19 transactions · 18 stateful · 2026-09-19 13:10:10 UTC
Parallelism
42/100
Blocked
56%
Avg conflicts / tx
2.11
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,185,413 · 19 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
1w02w13w24w35w06w411w512w613w714w815w916w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56409df0…27cd
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd41f5136…97c6
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x88e771e8…7d4a
0x34b655…2a6f
8 touches
6 conflicts
0x549c41f3…3e6c
0x34b655…2a6f
8 touches
6 conflicts
0xf90c6521…d8f0
0x34b655…2a6f
8 touches
6 conflicts
0x51f1f20c…d9da
0x34b655…2a6f
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
15 conflicts on slot 0x56409df050…ad27cd
Audit this contract →
← previous block·next block →recent activity