← previous blocknext block →recent activity
Analyzing
Block #106,186,209
26 transactions · 25 stateful · 2026-09-19 13:14:11 UTC
Parallelism
69/100
Blocked
52%
Avg conflicts / tx
1.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,186,209 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w47w58w614w115w223w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa3b4402…74e6
0x34b655…2a6f
16 touches
28 conflicts
0x05e1eba1…6491
0x34b655…2a6f
8 touches
6 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x71324cde…c3a2
0x34b655…2a6f
8 touches
6 conflicts
0xaa7079c5…fda4
0x34b655…2a6f
8 touches
6 conflicts
0x755c7b95…9404
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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
28 conflicts on slot 0xaa3b44023d…a974e6
Audit this contract →
← previous block·next block →recent activity