← previous blocknext block →recent activity

Analyzing

Block #99,992,672

27 transactions · 21 stateful · 2026-08-28 20:23:29 UTC

Parallelism

70/100

Blocked

43%

Avg conflicts / tx

1

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #99,992,672  ·  27 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

0xca841faa…486a

0x34b655…2a6f

14 touches
21 conflicts

0x36126dcb…ca1e

0x34b655…2a6f

6 touches
3 conflicts

0xfcd5e68f…2a12

0x34b655…2a6f

6 touches
3 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

6 touches
3 conflicts

0x3243e72f…1f6d

0x34b655…2a6f

4 touches
1 conflict

0x3af9ae89…1066

0x34b655…2a6f

4 touches
1 conflict

0x4a5956ef…e226

0x34b655…2a6f

4 touches
1 conflict

0x5969523e…5191

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 0xca841faae5…71486a

← previous block·next block →recent activity