← previous blocknext block →recent activity

Analyzing

Block #100,249,752

13 transactions · 12 stateful · 2026-08-29 17:58:33 UTC

Parallelism

85/100

Blocked

17%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #100,249,752  ·  13 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

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0x96ed54e2…04ed

0x34b655…2a6f

4 touches
1 conflict

0xb13b96bd…a3cb

0x34b655…2a6f

4 touches
1 conflict

0xf5c02069…d2cb

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x316f707b…07bc

0x34b655…2a6f

4 touches
1 conflict

0x316f707b…07bd

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 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity