← previous blocknext block →recent activity

Analyzing

Block #99,503,948

23 transactions · 20 stateful · 2026-08-27 03:09:36 UTC

Parallelism

74/100

Blocked

40%

Avg conflicts / tx

0.78

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #99,503,948  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xea57afd0…4232

0x34b655…2a6f

6 touches
3 conflicts

0x45885570…ed97

0x34b655…2a6f

4 touches
1 conflict

0x478cdc57…5f1d

0x34b655…2a6f

4 touches
1 conflict

0x48e2f58f…21cf

0x34b655…2a6f

4 touches
1 conflict

0x4c29ecd5…58b6

0x34b655…2a6f

4 touches
1 conflict

0x68292fe7…d918

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

10 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity