← previous blocknext block →recent activity

Analyzing

Block #95,746,469

7 transactions · 5 stateful · 2026-08-13 22:09:04 UTC

Parallelism

57/100

Blocked

40%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #95,746,469  ·  7 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

0x1b4aa556…0d2b

0x34b655…2a6f

4 touches
1 conflict

0x6f4e7625…aba5

0x34b655…2a6f

4 touches
1 conflict

0x966e45cf…0f25

0x34b655…2a6f

4 touches
1 conflict

0x9efba1b3…4d54

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xfbff297c…19ff

0x34b655…2a6f

4 touches
1 conflict

0x1703647e…b2c4

0x34b655…2a6f

2 touches
0 conflicts

0x19b34ad0…1b7b

0x34b655…2a6f

2 touches
0 conflicts

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 0x1b4aa556f0…0d0d2b

← previous block·next block →recent activity