← previous blocknext block →recent activity
Analyzing
Block #106,463,584
23 transactions · 21 stateful · 2026-09-20 12:30:14 UTC
Parallelism
61/100
Blocked
52%
Avg conflicts / tx
1.57
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,463,584 · 23 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w19w112w213w214w315w416w517w618w719w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63e4750c…d31e
0x34b655…2a6f
14 touches
21 conflicts
0xd563f3a1…94b1
0x34b655…2a6f
10 touches
10 conflicts
0x810a3aa2…0227
0x34b655…2a6f
10 touches
10 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
10 touches
10 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x07e7ae72…e93f
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x63e4750c83…dad31e
Audit this contract →
← previous block·next block →recent activity