← previous blocknext block →recent activity

Analyzing

Block #100,461,803

16 transactions · 14 stateful · 2026-08-30 11:48:28 UTC

Parallelism

81/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,461,803  ·  16 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

0x4c0a7fea…9446

0x34b655…2a6f

4 touches
1 conflict

0x9b2d3bee…8eeb

0x34b655…2a6f

4 touches
1 conflict

0x9b2d3bee…8eec

0x34b655…2a6f

4 touches
1 conflict

0x9c83a7b1…e305

0x34b655…2a6f

4 touches
1 conflict

0x9d8078fe…ed70

0x34b655…2a6f

4 touches
1 conflict

0x9dccd2a9…2790

0x34b655…2a6f

4 touches
1 conflict

0xa4c44fd7…19ef

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

1 conflict on slot 0x4c0a7fea33…a79446

← previous block·next block →recent activity