← previous blocknext block →recent activity
Analyzing
Block #105,849,714
23 transactions · 23 stateful · 2026-09-18 08:59:37 UTC
Parallelism
61/100
Blocked
57%
Avg conflicts / tx
2
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #105,849,714 · 23 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w08w110w211w312w413w514w615w721w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc947020…64da
0x34b655…2a6f
16 touches
28 conflicts
0x2827ae77…4368
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…001f
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
10 touches
10 conflicts
0xba5743c7…21c6
0x1b6862…e19c
10 touches
10 conflicts
0xc10b903d…2f54
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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 0xcc94702021…3d64da
Audit this contract →
← previous block·next block →recent activity