← previous blocknext block →recent activity

Analyzing

Block #95,714,375

20 transactions · 18 stateful · 2026-08-13 19:27:35 UTC

Parallelism

55/100

Blocked

56%

Avg conflicts / tx

1.7

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #95,714,375  ·  20 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xb3fb9fb5…64db

0x34b655…2a6f

12 touches
15 conflicts

0x734ee320…caae

0x34b655…2a6f

8 touches
6 conflicts

0xd3a4411d…81af

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x30ae635d…5e67

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xec7d120d…7084

0x34b655…2a6f

6 touches
3 conflicts

0x0a57a2b8…3cdd

0x34b655…2a6f

6 touches
3 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

15 conflicts on slot 0xb3fb9fb561…7664db

← previous block·next block →recent activity