← previous blocknext block →recent activity

Analyzing

Block #105,461,398

17 transactions · 16 stateful · 2026-09-17 00:23:46 UTC

Parallelism

88/100

Blocked

31%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #105,461,398  ·  17 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x00000000…004c

0x80c745…7210

4 touches
1 conflict

0x8d616e7c…a6a1

0x34b655…2a6f

4 touches
1 conflict

0xb40e601f…bf98

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xda50c9d5…674e

0x34b655…2a6f

4 touches
1 conflict

0xef7d55ff…6ffd

0x34b655…2a6f

4 touches
1 conflict

0xf5dc501b…8313

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: 0x80c74517…647210

1 conflict on slot 0x0000000000…00004c

← previous block·next block →recent activity