← previous blocknext block →recent activity

Analyzing

Block #100,588,652

16 transactions · 15 stateful · 2026-08-30 22:26:36 UTC

Parallelism

88/100

Blocked

27%

Avg conflicts / tx

0.38

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #100,588,652  ·  16 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x8649e48f…941c

0xc8689a…ee79

4 touches
1 conflict

0x0e18d182…0425

0x34b655…2a6f

4 touches
1 conflict

0x261cbea7…e35d

0x34b655…2a6f

4 touches
1 conflict

0x261cbea7…e35e

0x34b655…2a6f

4 touches
1 conflict

0x5730679c…b7d3

0x34b655…2a6f

4 touches
1 conflict

0x676f9f01…a8ac

0x34b655…2a6f

4 touches
1 conflict

0x7aad02c6…b979

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: Settlement / Helper

1 conflict on slot 0x8649e48f91…b7941c

← previous block·next block →recent activity