← previous blocknext block →recent activity
Analyzing
Block #106,435,357
19 transactions · 18 stateful · 2026-09-20 10:08:08 UTC
Parallelism
74/100
Blocked
33%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,435,357 · 19 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
1w02w14w25w36w07w18w09w116w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x228da3f5…c2bf
0x34b655…2a6f
10 touches
10 conflicts
0x3fa1fac4…826c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd563f3a1…94b1
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x5655f5c3…6b75
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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 0x228da3f59c…57c2bf
Audit this contract →
← previous block·next block →recent activity