← previous blocknext block →recent activity

Analyzing

Block #95,374,012

19 transactions · 17 stateful · 2026-08-12 14:53:04 UTC

Parallelism

84/100

Blocked

35%

Avg conflicts / tx

0.37

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #95,374,012  ·  19 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x4b6721e8…dd37

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0x1899cc94…2662

0x34b655…2a6f

4 touches
1 conflict

0x3c7c65d0…0b52

0x34b655…2a6f

4 touches
1 conflict

0x4efae872…6aa8

0x34b655…2a6f

4 touches
1 conflict

0x591f1ff5…d16c

0x34b655…2a6f

4 touches
1 conflict

0x69ee34d1…30f8

0x34b655…2a6f

4 touches
1 conflict

0x727fbce7…0c80

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

3 conflicts on slot 0x4b6721e84a…6edd37

← previous block·next block →recent activity