← previous blocknext block →recent activity
Analyzing
Block #105,852,469
43 transactions · 40 stateful · 2026-09-18 09:13:29 UTC
Parallelism
70/100
Blocked
63%
Avg conflicts / tx
2.33
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #105,852,469 · 43 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x55192654…91fe
0x34b655…2a6f
18 touches
36 conflicts
0x85794862…2ce2
0x34b655…2a6f
16 touches
28 conflicts
0xe0ccf17b…05b5
0xd32edf…ff58
15 touches
28 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0xd79c9727…1233
0x34b655…2a6f
10 touches
10 conflicts
0x25180879…8191
0x34b655…2a6f
10 touches
10 conflicts
0x89999c15…fdac
0x34b655…2a6f
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
36 conflicts on slot 0x551926541c…2e91fe
Audit this contract →
← previous block·next block →recent activity