← previous blocknext block →recent activity
Analyzing
Block #106,207,472
29 transactions · 25 stateful · 2026-09-19 15:01:14 UTC
Parallelism
79/100
Blocked
52%
Avg conflicts / tx
1.17
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,207,472 · 29 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
2w03w17w09w111w013w114w215w318w219w321w427w428w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a9e408e…3721
0x34b655…2a6f
10 touches
10 conflicts
0x839c0c71…bada
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x3643741b…109c
0x34b655…2a6f
8 touches
6 conflicts
0x366a19b0…f065
0x34b655…2a6f
8 touches
6 conflicts
0x419f4b7d…6f21
0x34b655…2a6f
8 touches
6 conflicts
0x4432679f…7a5c
0x34b655…2a6f
8 touches
6 conflicts
0x68292fe7…d918
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x6a9e408e97…fb3721
Audit this contract →
← previous block·next block →recent activity