← previous blocknext block →recent activity

Analyzing

Block #99,482,677

22 transactions · 19 stateful · 2026-08-27 01:22:32 UTC

Parallelism

82/100

Blocked

37%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #99,482,677  ·  22 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

0xea57afd0…4232

0x34b655…2a6f

6 touches
3 conflicts

0x5164ab0e…01e1

0xc8689a…ee79

4 touches
1 conflict

0x17c3727d…cb0e

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xcd3fb76b…8116

0x34b655…2a6f

4 touches
1 conflict

0xdcebb2b8…5f18

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 0xea57afd097…7f4232

← previous block·next block →recent activity