← previous blocknext block →recent activity
Analyzing
Block #106,915,984
35 transactions · 26 stateful · 2026-09-22 02:28:11 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,915,984 · 35 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
4w06w07w18w09w010w113w214w318w220w422w226w528w031w132w334w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6bd4088b…62b9
0x34b655…2a6f
10 touches
10 conflicts
0x6a9e408e…3721
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x06ec654f…48b7
0x34b655…2a6f
6 touches
3 conflicts
0x69411fb3…e36d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x654518db…3143
0xd32edf…ff58
5 touches
3 conflicts
0x366a19b0…f065
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
10 conflicts on slot 0x6bd4088b4e…5a62b9
Audit this contract →
← previous block·next block →recent activity