← previous blocknext block →recent activity

Analyzing

Block #99,264,475

25 transactions · 18 stateful · 2026-08-26 07:04:03 UTC

Parallelism

72/100

Blocked

50%

Avg conflicts / tx

0.72

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #99,264,475  ·  25 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x631b4113…baa9

0x34b655…2a6f

4 touches
1 conflict

0x651d4cdd…66a6

0x34b655…2a6f

4 touches
1 conflict

0x651d4cdd…66a7

0x34b655…2a6f

4 touches
1 conflict

0x71fad9ce…c11f

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x81238469…de5d

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

10 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity