← previous blocknext block →recent activity
Analyzing
Block #106,109,283
35 transactions · 32 stateful · 2026-09-19 06:47:02 UTC
Parallelism
69/100
Blocked
56%
Avg conflicts / tx
2.11
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,109,283 · 35 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
1w02w03w14w05w06w18w112w113w218w319w424w425w526w527w628w729w830w931w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26867cdc…dab5
0x34b655…2a6f
18 touches
36 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x961c0cd9…0937
0x34b655…2a6f
12 touches
15 conflicts
0x735a86cd…b64d
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x2a2896a0…2a0a
0x34b655…2a6f
10 touches
10 conflicts
0xb2560305…f27d
0x34b655…2a6f
10 touches
10 conflicts
0xeb09bf17…4364
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 0x26867cdcd7…bfdab5
Audit this contract →
← previous block·next block →recent activity