← previous blocknext block →recent activity
Analyzing
Block #106,187,099
29 transactions · 27 stateful · 2026-09-19 13:18:39 UTC
Parallelism
66/100
Blocked
67%
Avg conflicts / tx
2.07
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,187,099 · 29 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w28w39w410w511w612w715w119w220w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9430e759…86df
0x34b655…2a6f
18 touches
36 conflicts
0xb7e3e751…87fc
0x34b655…2a6f
12 touches
15 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
10 touches
10 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xe783dfa4…5499
0x1b6862…e19c
8 touches
6 conflicts
0x13c2d8a7…eb95
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
36 conflicts on slot 0x9430e759ab…3f86df
Audit this contract →
← previous block·next block →recent activity