← previous blocknext block →recent activity

Analyzing

Block #100,056,231

14 transactions · 14 stateful · 2026-08-29 01:43:26 UTC

Parallelism

79/100

Blocked

29%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,056,231  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x372c0c2c…abf9

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x758a0dd5…0f46

0x34b655…2a6f

4 touches
1 conflict

0x9e70dadd…810e

0x34b655…2a6f

4 touches
1 conflict

0x9ee73309…3c09

0x34b655…2a6f

4 touches
1 conflict

0xb1806df8…7d9a

0x34b655…2a6f

4 touches
1 conflict

0xb5924647…4cf1

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

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 0x372c0c2c29…1babf9

← previous block·next block →recent activity