← previous blocknext block →recent activity

Analyzing

Block #99,605,608

21 transactions · 21 stateful · 2026-08-27 11:46:13 UTC

Parallelism

67/100

Blocked

62%

Avg conflicts / tx

1.48

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #99,605,608  ·  21 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

0xca841faa…486a

0x34b655…2a6f

14 touches
21 conflicts

0x51af0e92…4020

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x258fcaf5…2084

0x34b655…2a6f

4 touches
1 conflict

0x46356904…5ead

0x34b655…2a6f

4 touches
1 conflict

0x4f4bdabd…ffba

0x34b655…2a6f

4 touches
1 conflict

0x63016070…64d5

0x34b655…2a6f

4 touches
1 conflict

0x6c1c8127…cba6

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