← previous blocknext block →recent activity
Analyzing
Block #106,385,789
17 transactions · 15 stateful · 2026-09-20 05:58:40 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,385,789 · 17 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
1w02w13w24w15w36w411w012w115w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d5222a8…ef79
0x34b655…2a6f
8 touches
6 conflicts
0xd2facdba…7a7e
0x34b655…2a6f
8 touches
6 conflicts
0x2130a548…c1de
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xdd77da90…6df4
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x5b37bb6b…ab00
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
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 0x7d5222a846…e1ef79
Audit this contract →
← previous block·next block →recent activity