← previous blocknext block →recent activity

Analyzing

Block #100,139,992

26 transactions · 16 stateful · 2026-08-29 08:45:17 UTC

Parallelism

92/100

Blocked

31%

Avg conflicts / tx

0.19

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #100,139,992  ·  26 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

0x54c6fb44…369a

0x34b655…2a6f

4 touches
1 conflict

0x00000000…004c

0x80c745…7210

4 touches
1 conflict

0x00000000…004b

0x80c745…7210

4 touches
1 conflict

0xb38f11d9…038b

0x34b655…2a6f

4 touches
1 conflict

0x932a9590…0b19

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

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 0x54c6fb4487…3b369a

← previous block·next block →recent activity