← previous blocknext block →recent activity

Analyzing

Block #99,253,910

20 transactions · 19 stateful · 2026-08-26 06:10:49 UTC

Parallelism

60/100

Blocked

47%

Avg conflicts / tx

1.25

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #99,253,910  ·  20 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x7e5ea60a…c4aa

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x92385428…6941

0x34b655…2a6f

10 touches
10 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

6 touches
3 conflicts

0x886db264…846e

0x34b655…2a6f

6 touches
3 conflicts

0x19760295…cf25

0xd32edf…ff58

5 touches
3 conflicts

0x95f13386…47be

0x34b655…2a6f

5 touches
3 conflicts

0x309f47c0…e1cf

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 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity