← previous blocknext block →recent activity
Analyzing
Block #106,198,025
38 transactions · 33 stateful · 2026-09-19 14:13:38 UTC
Parallelism
63/100
Blocked
70%
Avg conflicts / tx
3.32
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #106,198,025 · 38 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
1w02w13w24w35w46w57w68w724w125w226w328w429w530w631w732w833w934w1035w1136w1237w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
28 touches
91 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 conflicts
0x886db264…846e
0x34b655…2a6f
16 touches
28 conflicts
0x92385428…6941
0x34b655…2a6f
16 touches
28 conflicts
0x16fb02e7…bfc0
0xd32edf…ff58
15 touches
28 conflicts
0x21d8e673…067f
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x708d7a74…09e3
0x34b655…2a6f
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
91 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity