← previous blocknext block →recent activity

Analyzing

Block #99,985,712

15 transactions · 14 stateful · 2026-08-28 19:48:23 UTC

Parallelism

80/100

Blocked

43%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,985,712  ·  15 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xac9e0b10…4f67

0x34b655…2a6f

4 touches
1 conflict

0xcc282b3d…e139

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…004b

0x80c745…7210

4 touches
1 conflict

0x00000000…004c

0x80c745…7210

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x4f4bdabd…ffba

0x34b655…2a6f

4 touches
1 conflict

0x191e0467…70e5

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

1 conflict on slot 0xac9e0b10d0…ec4f67

← previous block·next block →recent activity