← previous blocknext block →recent activity

Analyzing

Block #95,559,265

25 transactions · 24 stateful · 2026-08-13 06:26:26 UTC

Parallelism

64/100

Blocked

42%

Avg conflicts / tx

1.12

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #95,559,265  ·  25 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x43fd3667…094b

0x34b655…2a6f

12 touches
15 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0x66d5e476…8a1f

0x34b655…2a6f

6 touches
3 conflicts

0xfb8c6cf4…01ee

0x34b655…2a6f

6 touches
3 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

4 touches
1 conflict

0xc423df8f…0264

0x34b655…2a6f

4 touches
1 conflict

0xd18e5a10…87ad

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

15 conflicts on slot 0x43fd366775…d0094b

← previous block·next block →recent activity