← previous blocknext block →recent activity

Analyzing

Block #95,031,946

19 transactions · 17 stateful · 2026-08-11 09:59:41 UTC

Parallelism

89/100

Blocked

12%

Avg conflicts / tx

0.16

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #95,031,946  ·  19 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x0abf7b77…0d80

0x34b655…2a6f

4 touches
1 conflict

0x4acbdbcf…a8c6

0x34b655…2a6f

4 touches
1 conflict

0x08636046…e60f

0x34b655…2a6f

4 touches
1 conflict

0x91b0f8ed…6bd6

0x34b655…2a6f

4 touches
1 conflict

0x91b0f8ed…6bd7

0x34b655…2a6f

4 touches
1 conflict

0xafb8e71e…9285

0x34b655…2a6f

4 touches
1 conflict

0xdba3b90b…02bd

0x34b655…2a6f

4 touches
1 conflict

0x3fed1570…be73

0x34b655…2a6f

2 touches
0 conflicts

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

1 conflict on slot 0x0abf7b7708…b00d80

← previous block·next block →recent activity