← previous blocknext block →recent activity
Analyzing
Block #106,389,205
31 transactions · 29 stateful · 2026-09-20 06:15:51 UTC
Parallelism
58/100
Blocked
66%
Avg conflicts / tx
2.58
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,389,205 · 31 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w713w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x075d2e3b…0fbc
0x34b655…2a6f
16 touches
28 conflicts
0x278d3acc…e70f
0xd32edf…ff58
15 touches
28 conflicts
0x0ea037c0…1ff4
0x34b655…2a6f
14 touches
21 conflicts
0xe283e878…7262
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…002a
0x1b6862…e19c
10 touches
10 conflicts
0xba5743c7…21c1
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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
28 conflicts on slot 0x075d2e3b11…ab0fbc
Audit this contract →
← previous block·next block →recent activity