← previous blocknext block →recent activity
Analyzing
Block #106,952,667
15 transactions · 15 stateful · 2026-09-22 05:32:50 UTC
Parallelism
53/100
Blocked
47%
Avg conflicts / tx
1.27
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,952,667 · 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
1w02w03w17w18w210w311w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x148c2efc…4410
0x34b655…2a6f
12 touches
15 conflicts
0xf58f6387…da5e
0x34b655…2a6f
8 touches
6 conflicts
0x363faadf…ea0a
0x34b655…2a6f
6 touches
3 conflicts
0xdf64e5e6…75e8
0x34b655…2a6f
4 touches
1 conflict
0xf0bc9977…25d3
0x34b655…2a6f
4 touches
1 conflict
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x9375a764…dca1
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
15 conflicts on slot 0x148c2efc85…b34410
Audit this contract →
← previous block·next block →recent activity