← previous blocknext block →recent activity

Analyzing

Block #99,194,593

23 transactions · 20 stateful · 2026-08-26 01:12:23 UTC

Parallelism

74/100

Blocked

40%

Avg conflicts / tx

0.78

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #99,194,593  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

10 touches
10 conflicts

0x62910921…3016

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x9a100e05…c541

0x34b655…2a6f

6 touches
3 conflicts

0x8714eb4d…e184

0x34b655…2a6f

4 touches
1 conflict

0xab3ad3dc…2a56

0x34b655…2a6f

4 touches
1 conflict

0xabfdfd0e…20bf

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

← previous block·next block →recent activity