← previous blocknext block →recent activity
Analyzing
Block #105,851,062
19 transactions · 17 stateful · 2026-09-18 09:06:24 UTC
Parallelism
68/100
Blocked
35%
Avg conflicts / tx
0.42
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,851,062 · 19 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
1w05w010w111w112w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7b7b345…1d04
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1d9867ad…6d9a
0x34b655…2a6f
4 touches
1 conflict
0x206f4379…e08a
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x6caf33e2…c261
0x34b655…2a6f
4 touches
1 conflict
0xaba718dc…57fc
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
3 conflicts on slot 0xc7b7b345d0…bc1d04
Audit this contract →
← previous block·next block →recent activity