← previous blocknext block →recent activity

Analyzing

Block #95,577,623

17 transactions · 17 stateful · 2026-08-13 07:58:45 UTC

Parallelism

59/100

Blocked

41%

Avg conflicts / tx

1.29

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,577,623  ·  17 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x95c47f03…f1bb

0x34b655…2a6f

14 touches
21 conflicts

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x0a57a2b8…3cdd

0x34b655…2a6f

4 touches
1 conflict

0x1ebd4745…6509

0x34b655…2a6f

4 touches
1 conflict

0x31519d10…f76b

0x34b655…2a6f

4 touches
1 conflict

0x4f473983…7d27

0x34b655…2a6f

4 touches
1 conflict

0x9000d2ee…2a11

0x34b655…2a6f

4 touches
1 conflict

0xa9a49465…0424

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

21 conflicts on slot 0x95c47f0322…51f1bb

← previous block·next block →recent activity