← previous blocknext block →recent activity

Analyzing

Block #100,055,332

17 transactions · 17 stateful · 2026-08-29 01:38:55 UTC

Parallelism

65/100

Blocked

47%

Avg conflicts / tx

1.35

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #100,055,332  ·  17 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

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xb240b520…a88a

0x34b655…2a6f

8 touches
6 conflicts

0x0490581d…adaf

0x34b655…2a6f

8 touches
6 conflicts

0xf6deafb5…5c25

0x34b655…2a6f

6 touches
3 conflicts

0x14b206bd…fd5e

0x34b655…2a6f

6 touches
3 conflicts

0x4a39a2a4…857b

0x34b655…2a6f

6 touches
3 conflicts

0xb482658a…e4f5

0x34b655…2a6f

6 touches
3 conflicts

0xc13e1d5c…62c6

0x34b655…2a6f

6 touches
3 conflicts

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 0x482471adbb…39122f

← previous block·next block →recent activity