← previous blocknext block →recent activity
Analyzing
Block #106,053,456
33 transactions · 29 stateful · 2026-09-19 02:06:05 UTC
Parallelism
70/100
Blocked
48%
Avg conflicts / tx
1.09
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,053,456 · 33 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w37w18w012w215w016w119w320w423w126w528w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x80fdc5be…7070
0x34b655…2a6f
8 touches
6 conflicts
0x07c47b1c…93c8
0x34b655…2a6f
6 touches
3 conflicts
0xab7f4e6b…8093
0x34b655…2a6f
4 touches
1 conflict
0xb2690dfb…2920
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity