← previous blocknext block →recent activity
Analyzing
Block #105,643,719
36 transactions · 33 stateful · 2026-09-17 15:41:25 UTC
Parallelism
72/100
Blocked
70%
Avg conflicts / tx
2.61
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,643,719 · 36 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w714w515w624w528w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42522e76…2592
0x34b655…2a6f
18 touches
36 conflicts
0xe8f5e33f…719c
0x34b655…2a6f
18 touches
36 conflicts
0x8968fc32…20e3
0x34b655…2a6f
16 touches
28 conflicts
0x6771eae2…7014
0x34b655…2a6f
16 touches
28 conflicts
0x2747bbde…8e7f
0xd32edf…ff58
15 touches
28 conflicts
0x35801c67…bcc1
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 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 0x42522e76ce…082592
Audit this contract →
← previous block·next block →recent activity