← previous blocknext block →recent activity

Analyzing

Block #99,490,058

17 transactions · 17 stateful · 2026-08-27 01:59:42 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.82

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #99,490,058  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x36918c55…8424

0x34b655…2a6f

6 touches
3 conflicts

0xea57afd0…4232

0x34b655…2a6f

6 touches
3 conflicts

0x36126dcb…ca1e

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0018

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0028

0x1b6862…e19c

4 touches
1 conflict

0x6fd9ae7c…e97d

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x077d58c3…8ed7

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

3 conflicts on slot 0x36918c5535…2c8424

← previous block·next block →recent activity