← previous blocknext block →recent activity

Analyzing

Block #100,609,512

20 transactions · 18 stateful · 2026-08-31 00:11:33 UTC

Parallelism

80/100

Blocked

39%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #100,609,512  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…004f

0x80c745…7210

4 touches
1 conflict

0x00000000…004c

0x80c745…7210

4 touches
1 conflict

0x5f77d607…2c84

0x065c9d…c394

4 touches
1 conflict

0xf98c943e…7c44

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001f

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb87

0x1b6862…e19c

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity