← previous blocknext block →recent activity
Analyzing
Block #106,423,316
33 transactions · 30 stateful · 2026-09-20 09:07:31 UTC
Parallelism
85/100
Blocked
40%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,423,316 · 33 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
1w04w05w17w08w19w210w113w118w019w123w224w225w326w327w431w032w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0acbae3f…9d02
0x34b655…2a6f
10 touches
10 conflicts
0x3b53436c…2ec3
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x000bde1a…e123
0x34b655…2a6f
6 touches
3 conflicts
0x3b22ed54…b185
0x34b655…2a6f
6 touches
3 conflicts
0x502b3ee1…7f7c
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 0x0acbae3f42…fa9d02
Audit this contract →
← previous block·next block →recent activity