← previous blocknext block →recent activity

Analyzing

Block #96,837,862

21 transactions · 19 stateful · 2026-08-17 17:39:13 UTC

Parallelism

57/100

Blocked

58%

Avg conflicts / tx

1.1

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #96,837,862  ·  21 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

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xe6e6f436…ddc0

0x34b655…2a6f

8 touches
6 conflicts

0x9efa015f…8509

0xd32edf…ff58

7 touches
6 conflicts

0xd8bc53a3…c2fe

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x96fed898…e5ba

0x34b655…2a6f

6 touches
3 conflicts

0x24e578ef…2049

0x34b655…2a6f

6 touches
3 conflicts

0x34a1ee7e…fb20

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

6 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity