← previous blocknext block →recent activity
Analyzing
Block #105,608,260
20 transactions · 19 stateful · 2026-09-17 12:42:54 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,608,260 · 20 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
1w02w13w17w28w09w111w312w415w416w519w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x48132b64…8e95
0x34b655…2a6f
12 touches
15 conflicts
0xa7ecbbe7…f713
0x34b655…2a6f
10 touches
10 conflicts
0x35b0198e…3e0d
0x34b655…2a6f
6 touches
3 conflicts
0x0a2131b3…455e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x6771eae2…7014
0x34b655…2a6f
4 touches
1 conflict
0x69011797…547a
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
15 conflicts on slot 0x48132b64b3…4d8e95
Audit this contract →
← previous block·next block →recent activity