← previous blocknext block →recent activity

Analyzing

Block #99,880,653

23 transactions · 21 stateful · 2026-08-28 10:59:01 UTC

Parallelism

78/100

Blocked

38%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,880,653  ·  23 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

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe41a834d…a88a

0x34b655…2a6f

4 touches
1 conflict

0x184a9b09…c825

0x34b655…2a6f

4 touches
1 conflict

0x41469894…598f

0x34b655…2a6f

4 touches
1 conflict

0x41469894…5990

0x34b655…2a6f

4 touches
1 conflict

0x62bb20db…431e

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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