← previous blocknext block →recent activity

Analyzing

Block #99,155,584

23 transactions · 20 stateful · 2026-08-25 21:56:07 UTC

Parallelism

70/100

Blocked

45%

Avg conflicts / tx

0.83

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #99,155,584  ·  23 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

12 touches
15 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

8 touches
6 conflicts

0xbd590df7…9891

0x34b655…2a6f

8 touches
6 conflicts

0xb0f5d668…99ac

0x34b655…2a6f

8 touches
6 conflicts

0x67cfcfc2…78dd

0x34b655…2a6f

7 touches
6 conflicts

0xfcd5e68f…2a12

0x34b655…2a6f

6 touches
3 conflicts

0x5ecbbe42…e861

0x34b655…2a6f

4 touches
1 conflict

0x6fbc2e5a…e69c

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity