← previous blocknext block →recent activity

Analyzing

Block #95,745,839

16 transactions · 16 stateful · 2026-08-13 22:05:54 UTC

Parallelism

56/100

Blocked

50%

Avg conflicts / tx

1.06

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,745,839  ·  16 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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xf0d45ffd…89cf

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x34d95d94…3a16

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xeae24c…0be0

4 touches
1 conflict

0x0a57a2b8…3cdd

0x34b655…2a6f

4 touches
1 conflict

0x0d488000…3831

0x34b655…2a6f

4 touches
1 conflict

0x5e0b8bbe…377b

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

6 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity