← previous blocknext block →recent activity

Analyzing

Block #95,655,557

23 transactions · 22 stateful · 2026-08-13 14:30:46 UTC

Parallelism

74/100

Blocked

36%

Avg conflicts / tx

0.78

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,655,557  ·  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

0x00000000…0031

0x59df86…2780

12 touches
15 conflicts

0x160f117d…8e90

0x065c9d…c394

4 touches
1 conflict

0xb33ff823…1188

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002c

0x1b6862…e19c

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: 0x59df8637…6d2780

15 conflicts on slot 0x0000000000…000031

← previous block·next block →recent activity