← previous blocknext block →recent activity

Analyzing

Block #95,655,452

27 transactions · 15 stateful · 2026-08-13 14:30:14 UTC

Parallelism

78/100

Blocked

47%

Avg conflicts / tx

0.56

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,655,452  ·  27 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

0xf0d45ffd…89cf

0x34b655…2a6f

6 touches
3 conflicts

0x1526b11f…8b21

0x34b655…2a6f

6 touches
3 conflicts

0x78affea8…5ca2

0x34b655…2a6f

6 touches
3 conflicts

0x7be3246e…f89f

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x31b39922…1e66

0x34b655…2a6f

4 touches
1 conflict

0x3b9bb58c…e73a

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 0xf0d45ffdb0…4089cf

← previous block·next block →recent activity