← previous blocknext block →recent activity

Analyzing

Block #99,477,108

24 transactions · 22 stateful · 2026-08-27 00:54:26 UTC

Parallelism

79/100

Blocked

32%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,477,108  ·  24 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x939cdd56…00c8

0x34b655…2a6f

8 touches
6 conflicts

0xdcebb2b8…5f18

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xd5982776…4846

0x34b655…2a6f

6 touches
3 conflicts

0x593cce97…57ff

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0xa0f10008…b6a3

0x34b655…2a6f

5 touches
3 conflicts

0x9acf14c9…c33d

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

6 conflicts on slot 0x939cdd567e…a300c8

← previous block·next block →recent activity