← previous blocknext block →recent activity
Analyzing
Block #106,930,594
15 transactions · 14 stateful · 2026-09-22 03:41:43 UTC
Parallelism
53/100
Blocked
57%
Avg conflicts / tx
0.93
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,930,594 · 15 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w59w613w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fad6fee…7714
0x34b655…2a6f
8 touches
6 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0x810a3aa2…0227
0x34b655…2a6f
8 touches
6 conflicts
0xb0b4018e…629b
0x34b655…2a6f
8 touches
6 conflicts
0xb6a59002…65eb
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x704a8131…bbe8
0x34b655…2a6f
4 touches
1 conflict
0x43080f0f…7ffe
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 0x5fad6fee64…277714
Audit this contract →
← previous block·next block →recent activity