← previous blocknext block →recent activity
Analyzing
Block #106,953,490
20 transactions · 16 stateful · 2026-09-22 05:36:58 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,953,490 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w19w211w312w013w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x772354e9…ae44
0x34b655…2a6f
10 touches
10 conflicts
0x3eb48ea2…eef2
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xa9988419…9f45
0x34b655…2a6f
6 touches
3 conflicts
0xab41643c…f9bf
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x26bb6db7…f861
0x1b6862…e19c
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
10 conflicts on slot 0x772354e9e7…8cae44
Audit this contract →
← previous block·next block →recent activity