← previous blocknext block →recent activity
Analyzing
Block #106,554,099
33 transactions · 24 stateful · 2026-09-20 20:05:47 UTC
Parallelism
79/100
Blocked
63%
Avg conflicts / tx
1.36
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,554,099 · 33 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w07w19w211w313w416w521w322w423w524w627w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc8fb280…76a3
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x72d35c7e…525e
0x34b655…2a6f
10 touches
10 conflicts
0xb5cdcafb…51e2
0x34b655…2a6f
10 touches
10 conflicts
0xb8a4b8a7…e631
0x34b655…2a6f
10 touches
10 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
10 touches
10 conflicts
0x556beb43…e627
0x34b655…2a6f
8 touches
6 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0xbc8fb28081…2176a3
Audit this contract →
← previous block·next block →recent activity