← previous blocknext block →recent activity
Analyzing
Block #106,272,661
24 transactions · 23 stateful · 2026-09-19 20:29:22 UTC
Parallelism
75/100
Blocked
39%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,272,661 · 24 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
1w02w15w07w09w110w217w118w219w220w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7bb4e098…a360
0x34b655…2a6f
10 touches
10 conflicts
0x4984f7be…d515
0x34b655…2a6f
8 touches
6 conflicts
0x1cdfe548…d3aa
0x34b655…2a6f
8 touches
6 conflicts
0x8028595c…1e10
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
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
10 conflicts on slot 0x7bb4e098a9…09a360
Audit this contract →
← previous block·next block →recent activity