← previous blocknext block →recent activity

Analyzing

Block #100,119,096

17 transactions · 16 stateful · 2026-08-29 06:59:57 UTC

Parallelism

88/100

Blocked

19%

Avg conflicts / tx

0.24

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #100,119,096  ·  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

0x50812214…4dcd

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe1c4e5ce…0dec

0x34b655…2a6f

4 touches
1 conflict

0xe2d50773…c39e

0x34b655…2a6f

4 touches
1 conflict

0x70a7b5d6…fe0e

0x34b655…2a6f

4 touches
1 conflict

0x21e79ad8…c5db

0x34b655…2a6f

4 touches
1 conflict

0x37a5d2b7…25f0

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

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 0x50812214e9…464dcd

← previous block·next block →recent activity