← previous blocknext block →recent activity

Analyzing

Block #100,431,487

30 transactions · 25 stateful · 2026-08-30 09:15:52 UTC

Parallelism

87/100

Blocked

20%

Avg conflicts / tx

0.3

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #100,431,487  ·  30 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x1db5837f…1264

0x34b655…2a6f

6 touches
3 conflicts

0xac808a27…82db

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0xaa4fe105…eccc

0x34b655…2a6f

4 touches
1 conflict

0xb9b077a8…e029

0x34b655…2a6f

4 touches
1 conflict

0xc401f6db…0204

0x34b655…2a6f

4 touches
1 conflict

0xcb334a17…b16e

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 0x1db5837f6b…d01264

← previous block·next block →recent activity