← previous blocknext block →recent activity

Analyzing

Block #95,297,732

20 transactions · 19 stateful · 2026-08-12 08:26:36 UTC

Parallelism

70/100

Blocked

42%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,297,732  ·  20 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x28e32856…45f6

0x34b655…2a6f

4 touches
1 conflict

0x2edb0a6e…06c3

0x34b655…2a6f

4 touches
1 conflict

0x48b8d2e5…3f2f

0x34b655…2a6f

4 touches
1 conflict

0x4d1d85aa…01a0

0x34b655…2a6f

4 touches
1 conflict

0x64a785e4…0110

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity