← previous blocknext block →recent activity

Analyzing

Block #96,624,522

18 transactions · 14 stateful · 2026-08-16 23:46:12 UTC

Parallelism

61/100

Blocked

50%

Avg conflicts / tx

1.11

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #96,624,522  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x7de57974…f5ba

0x34b655…2a6f

8 touches
6 conflicts

0x061891da…90c1

0x34b655…2a6f

8 touches
6 conflicts

0xe22ab637…7a8e

0x34b655…2a6f

8 touches
6 conflicts

0x8a5ced1c…3b29

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0xa7481e1f…531f

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

10 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity