← previous blocknext block →recent activity
Analyzing
Block #106,538,410
14 transactions · 13 stateful · 2026-09-20 18:46:49 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,538,410 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w17w08w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46a5ec6c…f318
0x34b655…2a6f
4 touches
1 conflict
0xb5bf6c79…b71a
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x3167d7d8…a06b
0x34b655…2a6f
2 touches
0 conflicts
0x75a69dd9…8f57
0x34b655…2a6f
2 touches
0 conflicts
0xa3ff1ab2…8ae3
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x46a5ec6cde…19f318
Audit this contract →
← previous block·next block →recent activity