← previous blocknext block →recent activity

Analyzing

Block #98,503,137

21 transactions · 18 stateful · 2026-08-23 14:31:32 UTC

Parallelism

86/100

Blocked

28%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,503,137  ·  21 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

0x261cbea7…e35e

0x34b655…2a6f

4 touches
1 conflict

0x398e1fec…f13e

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x4b544c60…d984

0x34b655…2a6f

4 touches
1 conflict

0x7aad02c6…b979

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…004c

0x80c745…7210

4 touches
1 conflict

0x00000000…004f

0x80c745…7210

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 0x261cbea79d…12e35e

← previous block·next block →recent activity