← previous blocknext block →recent activity

Analyzing

Block #95,349,107

25 transactions · 22 stateful · 2026-08-12 12:46:52 UTC

Parallelism

56/100

Blocked

55%

Avg conflicts / tx

1.28

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #95,349,107  ·  25 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xca841faa…486a

0x34b655…2a6f

12 touches
15 conflicts

0x95c47f03…f1bb

0x34b655…2a6f

10 touches
10 conflicts

0xec7d120d…7084

0x34b655…2a6f

6 touches
3 conflicts

0x23d51e55…82c2

0x34b655…2a6f

6 touches
3 conflicts

0xa15e2d91…025a

0x34b655…2a6f

6 touches
3 conflicts

0x7b67f6cf…0aab

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x82a98670…fb5f

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 0xca841faae5…71486a

← previous block·next block →recent activity