← previous blocknext block →recent activity

Analyzing

Block #96,836,245

21 transactions · 21 stateful · 2026-08-17 17:31:06 UTC

Parallelism

52/100

Blocked

62%

Avg conflicts / tx

2.05

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #96,836,245  ·  21 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0xec7d120d…7084

0x34b655…2a6f

10 touches
10 conflicts

0x734ee320…caae

0x34b655…2a6f

8 touches
6 conflicts

0x52b477bc…7ccf

0x34b655…2a6f

8 touches
6 conflicts

0x3e72a2d1…ce0e

0x34b655…2a6f

8 touches
6 conflicts

0x45ea7a97…bbb3

0x34b655…2a6f

6 touches
3 conflicts

0x4cabb80a…46bf

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 0xc824469a90…af6425

← previous block·next block →recent activity