← previous blocknext block →recent activity
Analyzing
Block #106,453,513
20 transactions · 19 stateful · 2026-09-20 11:39:33 UTC
Parallelism
60/100
Blocked
58%
Avg conflicts / tx
1.55
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,453,513 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w16w28w39w410w511w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c2fc330…0091
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xa5811d93…8c73
0x34b655…2a6f
8 touches
6 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x2ad29ab6…03e0
0x34b655…2a6f
8 touches
6 conflicts
0x18fd3f6d…cb73
0x34b655…2a6f
8 touches
6 conflicts
0xc3baa205…f26e
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x9c2fc33042…7d0091
Audit this contract →
← previous block·next block →recent activity