← previous blocknext block →recent activity

Analyzing

Block #99,659,165

20 transactions · 20 stateful · 2026-08-27 16:18:06 UTC

Parallelism

65/100

Blocked

40%

Avg conflicts / tx

1.45

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #99,659,165  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x886db264…846e

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0xbdc4532a…8b52

0x34b655…2a6f

6 touches
3 conflicts

0x9708602e…de14

0x34b655…2a6f

6 touches
3 conflicts

0x4a8c8175…cb89

0x34b655…2a6f

4 touches
1 conflict

0xf3d10975…0d07

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity