← previous blocknext block →recent activity
Analyzing
Block #106,281,768
22 transactions · 21 stateful · 2026-09-19 21:15:11 UTC
Parallelism
50/100
Blocked
57%
Avg conflicts / tx
2.59
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,281,768 · 22 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w07w18w210w311w413w514w615w716w817w918w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x885efce3…7496
0x34b655…2a6f
20 touches
45 conflicts
0xb4634dcc…b675
0x34b655…2a6f
16 touches
28 conflicts
0xe7738a9b…bac3
0x34b655…2a6f
10 touches
10 conflicts
0x94e7f277…471b
0x34b655…2a6f
8 touches
6 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
8 touches
6 conflicts
0x5850dde5…44f6
0x34b655…2a6f
8 touches
6 conflicts
0xe098738f…9bbe
0x34b655…2a6f
8 touches
6 conflicts
0x8fb6bad3…adeb
0x34b655…2a6f
6 touches
3 conflicts
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
45 conflicts on slot 0x885efce3b0…367496
Audit this contract →
← previous block·next block →recent activity