← previous blocknext block →recent activity
Analyzing
Block #106,434,627
31 transactions · 19 stateful · 2026-09-20 10:04:27 UTC
Parallelism
90/100
Blocked
26%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,434,627 · 31 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w09w111w012w123w024w025w127w028w230w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb111bae…5303
0x34b655…2a6f
6 touches
3 conflicts
0xcd9ba26b…108d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x2836d18c…d85c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x9ff4ca89…6115
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
3 conflicts on slot 0xfb111bae3a…475303
Audit this contract →
← previous block·next block →recent activity