← previous blocknext block →recent activity

Analyzing

Block #95,655,284

21 transactions · 19 stateful · 2026-08-13 14:29:24 UTC

Parallelism

71/100

Blocked

42%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

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

0xb56f0740…7542

0x34b655…2a6f

6 touches
3 conflicts

0xb7184392…a0f6

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x3b9c6379…defb

0x34b655…2a6f

4 touches
1 conflict

0x6e6a8155…9636

0x34b655…2a6f

4 touches
1 conflict

0x706c758c…2fdb

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

15 conflicts on slot 0x0000000000…000031

← previous block·next block →recent activity