← previous blocknext block →recent activity
Analyzing
Block #106,188,565
23 transactions · 21 stateful · 2026-09-19 13:26:02 UTC
Parallelism
74/100
Blocked
52%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,188,565 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w16w07w28w09w113w314w216w317w018w120w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x581b829b…9578
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd62f3741…b903
0x34b655…2a6f
6 touches
3 conflicts
0x3dadb22d…64df
0x34b655…2a6f
6 touches
3 conflicts
0x9256b810…52cd
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
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
6 conflicts on slot 0x581b829b39…8f9578
Audit this contract →
← previous block·next block →recent activity