← previous blocknext block →recent activity

Analyzing

Block #99,485,941

20 transactions · 19 stateful · 2026-08-27 01:38:58 UTC

Parallelism

70/100

Blocked

42%

Avg conflicts / tx

0.8

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #99,485,941  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xb3fb9fb5…64db

0x34b655…2a6f

4 touches
1 conflict

0xb903303a…fb31

0x34b655…2a6f

4 touches
1 conflict

0x00500a94…20d5

0x34b655…2a6f

4 touches
1 conflict

0x192a1fc3…9766

0x34b655…2a6f

4 touches
1 conflict

0x1b72bb2a…ceea

0x34b655…2a6f

4 touches
1 conflict

0x2ad2f4bc…1800

0x34b655…2a6f

4 touches
1 conflict

0x33000c0a…82c3

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