← previous blocknext block →recent activity

Analyzing

Block #100,631,631

22 transactions · 20 stateful · 2026-08-31 02:02:49 UTC

Parallelism

64/100

Blocked

45%

Avg conflicts / tx

1

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #100,631,631  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x5ed1f9d0…fc7f

0x34b655…2a6f

12 touches
15 conflicts

0x7401eb95…986b

0x34b655…2a6f

8 touches
6 conflicts

0x9ff4ca89…6115

0x34b655…2a6f

6 touches
3 conflicts

0xbee5cfda…5e91

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x6674a6df…0368

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0xa11b60f7…8e8b

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

15 conflicts on slot 0x5ed1f9d00b…62fc7f

← previous block·next block →recent activity