← previous blocknext block →recent activity
Analyzing
Block #106,184,669
26 transactions · 24 stateful · 2026-09-19 13:06:26 UTC
Parallelism
77/100
Blocked
46%
Avg conflicts / tx
1.04
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,184,669 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w07w48w09w110w111w112w216w217w225w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07c47b1c…93c8
0x34b655…2a6f
12 touches
15 conflicts
0xd193364c…cd91
0x34b655…2a6f
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xdf64e5e6…75e8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x523a970e…97c0
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
15 conflicts on slot 0x07c47b1ce2…b693c8
Audit this contract →
← previous block·next block →recent activity