← previous blocknext block →recent activity

Analyzing

Block #95,902,098

23 transactions · 22 stateful · 2026-08-14 11:12:00 UTC

Parallelism

61/100

Blocked

55%

Avg conflicts / tx

1.43

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #95,902,098  ·  23 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

10 touches
10 conflicts

0x53f393fa…00b9

0x34b655…2a6f

10 touches
10 conflicts

0x4acbdbcf…a8c6

0x34b655…2a6f

8 touches
6 conflicts

0xa3a621f8…75a2

0x34b655…2a6f

6 touches
3 conflicts

0x54998534…d4dd

0x34b655…2a6f

4 touches
1 conflict

0x57b57f51…2449

0x34b655…2a6f

4 touches
1 conflict

0x98862f54…62ca

0x34b655…2a6f

4 touches
1 conflict

0xa27f1875…0c5d

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

10 conflicts on slot 0xb3fb9fb561…7664db

← previous block·next block →recent activity