← previous blocknext block →recent activity

Analyzing

Block #105,617,770

21 transactions · 20 stateful · 2026-09-17 13:30:47 UTC

Parallelism

86/100

Blocked

30%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #105,617,770  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xeb5b61a2…b2bc

0x34b655…2a6f

4 touches
1 conflict

0xf06fce24…887d

0x34b655…2a6f

4 touches
1 conflict

0x00000000…004b

0x80c745…7210

4 touches
1 conflict

0x00000000…004c

0x80c745…7210

4 touches
1 conflict

0x31e0d360…e742

0x34b655…2a6f

4 touches
1 conflict

0x42522e76…2592

0x34b655…2a6f

4 touches
1 conflict

0x49890ced…6f23

0x34b655…2a6f

4 touches
1 conflict

0x52cb7a4c…8906

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

1 conflict on slot 0xeb5b61a29c…4fb2bc

← previous block·next block →recent activity