← previous blocknext block →recent activity

Analyzing

Block #100,063,302

20 transactions · 20 stateful · 2026-08-29 02:19:01 UTC

Parallelism

70/100

Blocked

40%

Avg conflicts / tx

0.8

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #100,063,302  ·  20 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

0x0efc210e…70ab

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x639be938…49c4

0x34b655…2a6f

6 touches
3 conflicts

0x531ade44…ad45

0x34b655…2a6f

4 touches
1 conflict

0x684b830d…d19e

0x34b655…2a6f

4 touches
1 conflict

0x6d5c5d72…914b

0x34b655…2a6f

4 touches
1 conflict

0xa5811d93…8c73

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 0x0efc210ee8…0e70ab

← previous block·next block →recent activity