← previous blocknext block →recent activity
Analyzing
Block #106,191,198
14 transactions · 13 stateful · 2026-09-19 13:39:17 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,191,198 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w110w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8dd36ab5…9da1
0x34b655…2a6f
4 touches
1 conflict
0xd4305f3b…7f3e
0x34b655…2a6f
4 touches
1 conflict
0xd597209e…9800
0x34b655…2a6f
4 touches
1 conflict
0xfe5f5aab…21d7
0x34b655…2a6f
4 touches
1 conflict
0x07c47b1c…93c8
0x34b655…2a6f
4 touches
1 conflict
0x315e07b8…9823
0x34b655…2a6f
4 touches
1 conflict
0x27ff4dfd…538b
0xd32edf…ff58
3 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
2 touches
0 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
1 conflict on slot 0x8dd36ab523…6d9da1
Audit this contract →
← previous block·next block →recent activity