← previous blocknext block →recent activity

Analyzing

Block #100,587,908

24 transactions · 21 stateful · 2026-08-30 22:22:51 UTC

Parallelism

79/100

Blocked

38%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,587,908  ·  24 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x1d9154e7…8821

0x34b655…2a6f

4 touches
1 conflict

0x2cc3b76e…8b93

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x9c6a9da2…c628

0x34b655…2a6f

4 touches
1 conflict

0xf984d8ab…6e4f

0x34b655…2a6f

4 touches
1 conflict

0xde54926c…1c87

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