← previous blocknext block →recent activity

Analyzing

Block #95,719,174

19 transactions · 17 stateful · 2026-08-13 19:51:48 UTC

Parallelism

68/100

Blocked

41%

Avg conflicts / tx

0.63

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,719,174  ·  19 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

0x0a57a2b8…3cdd

0x34b655…2a6f

8 touches
6 conflicts

0x982900c0…d7a7

0x34b655…2a6f

6 touches
3 conflicts

0xafb8e71e…9285

0x34b655…2a6f

6 touches
3 conflicts

0x30c5329c…711c

0x34b655…2a6f

4 touches
1 conflict

0x3cf099ce…2802

0x34b655…2a6f

4 touches
1 conflict

0x410b84ab…1dbc

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x522e20b4…fbc4

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 0x0a57a2b8cd…773cdd

← previous block·next block →recent activity