← previous blocknext block →recent activity

Analyzing

Block #100,156,540

19 transactions · 19 stateful · 2026-08-29 10:08:36 UTC

Parallelism

68/100

Blocked

42%

Avg conflicts / tx

0.74

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #100,156,540  ·  19 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xe1c4e5ce…0dec

0x34b655…2a6f

6 touches
3 conflicts

0xbd590df7…9891

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x4c29ecd5…58b6

0x34b655…2a6f

6 touches
3 conflicts

0x386e26c3…fa30

0x34b655…2a6f

4 touches
1 conflict

0x55e31fcc…6111

0x34b655…2a6f

4 touches
1 conflict

0x86bf7578…c38f

0x34b655…2a6f

4 touches
1 conflict

0xab2b11cd…7e41

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

3 conflicts on slot 0xe1c4e5ce15…770dec

← previous block·next block →recent activity