← previous blocknext block →recent activity

Analyzing

Block #99,457,190

19 transactions · 16 stateful · 2026-08-26 23:14:10 UTC

Parallelism

89/100

Blocked

31%

Avg conflicts / tx

0.32

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #99,457,190  ·  19 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xea57afd0…4232

0x34b655…2a6f

4 touches
1 conflict

0x7aad02c6…b979

0x34b655…2a6f

4 touches
1 conflict

0xa56ae218…1fc5

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…641e

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…641f

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

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 0xea57afd097…7f4232

← previous block·next block →recent activity