← previous blocknext block →recent activity

Analyzing

Block #95,654,744

24 transactions · 24 stateful · 2026-08-13 14:26:41 UTC

Parallelism

71/100

Blocked

38%

Avg conflicts / tx

1.04

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,654,744  ·  24 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

0x00000000…0031

0x59df86…2780

14 touches
21 conflicts

0x00ddbbf2…4588

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x26e514e6…873a

0x34b655…2a6f

4 touches
1 conflict

0x21d22421…0b7a

0x34b655…2a6f

4 touches
1 conflict

0x7be3246e…f89f

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

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

21 conflicts on slot 0x0000000000…000031

← previous block·next block →recent activity