← previous blocknext block →recent activity
Analyzing
Block #106,109,364
12 transactions · 11 stateful · 2026-09-19 06:47:26 UTC
Parallelism
58/100
Blocked
45%
Avg conflicts / tx
1.08
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,109,364 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w07w18w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbaa018bc…2b2f
0x34b655…2a6f
8 touches
6 conflicts
0x4e58f1d6…2fca
0x34b655…2a6f
8 touches
6 conflicts
0x735a86cd…b64d
0x34b655…2a6f
8 touches
6 conflicts
0x961c0cd9…0937
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xbaa018bc62…432b2f
Audit this contract →
← previous block·next block →recent activity