← previous blocknext block →recent activity

Analyzing

Block #100,809,824

35 transactions · 26 stateful · 2026-08-31 16:59:23 UTC

Parallelism

80/100

Blocked

31%

Avg conflicts / tx

0.54

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #100,809,824  ·  35 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

8 touches
6 conflicts

0xd9722304…6ed0

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x301e92c3…2616

0x34b655…2a6f

4 touches
1 conflict

0x3e0aba4b…12ad

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5784baac…ac7e

0x34b655…2a6f

4 touches
1 conflict

0x76622fb2…4f08

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

6 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity