← previous blocknext block →recent activity
Analyzing
Block #106,951,912
17 transactions · 16 stateful · 2026-09-22 05:29:02 UTC
Parallelism
65/100
Blocked
31%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,951,912 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w19w210w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54ca5b2f…67c2
0x34b655…2a6f
12 touches
15 conflicts
0x75ba2439…a9d6
0x34b655…2a6f
10 touches
10 conflicts
0xef5959a3…2a2f
0x34b655…2a6f
6 touches
3 conflicts
0xa9988419…9f45
0x34b655…2a6f
6 touches
3 conflicts
0xab41643c…f9bf
0x34b655…2a6f
6 touches
3 conflicts
0x5fad6fee…7714
0x34b655…2a6f
4 touches
1 conflict
0x3eb48ea2…eef2
0x34b655…2a6f
4 touches
1 conflict
0x49b9fdd5…9c16
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 0x54ca5b2f10…1f67c2
Audit this contract →
← previous block·next block →recent activity