← previous blocknext block →recent activity

Analyzing

Block #100,612,315

22 transactions · 20 stateful · 2026-08-31 00:25:39 UTC

Parallelism

68/100

Blocked

40%

Avg conflicts / tx

0.86

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #100,612,315  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x1a5c0d2f…7301

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xdfce7dfe…5053

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0x00f19757…9252

0x34b655…2a6f

4 touches
1 conflict

0x0476d77b…a514

0x34b655…2a6f

4 touches
1 conflict

0x15698ac9…2a46

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

6 conflicts on slot 0x1a5c0d2fa1…937301

← previous block·next block →recent activity