← previous blocknext block →recent activity

Analyzing

Block #100,812,183

16 transactions · 12 stateful · 2026-08-31 17:11:15 UTC

Parallelism

88/100

Blocked

25%

Avg conflicts / tx

0.19

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #100,812,183  ·  16 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

0xa5b4eb1b…616b

0x34b655…2a6f

4 touches
1 conflict

0xa952c504…7b64

0x34b655…2a6f

4 touches
1 conflict

0x1867b653…e61b

0x34b655…2a6f

4 touches
1 conflict

0xdb77443f…c933

0x34b655…2a6f

4 touches
1 conflict

0xdd72b9bf…0b10

0x34b655…2a6f

4 touches
1 conflict

0xf38a3927…ad62

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x49890ced…6f23

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 0xa5b4eb1ba4…5d616b

← previous block·next block →recent activity