← previous blocknext block →recent activity

Analyzing

Block #96,684,341

21 transactions · 17 stateful · 2026-08-17 04:47:03 UTC

Parallelism

67/100

Blocked

53%

Avg conflicts / tx

1.62

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #96,684,341  ·  21 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

0x53f393fa…00b9

0x34b655…2a6f

14 touches
21 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

10 touches
10 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

8 touches
6 conflicts

0xfbe6a366…8ca1

0x34b655…2a6f

6 touches
3 conflicts

0x19e69334…a345

0x34b655…2a6f

6 touches
3 conflicts

0xb856a9e9…9da3

0x34b655…2a6f

6 touches
3 conflicts

0xec7d120d…7084

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

21 conflicts on slot 0x53f393fafd…2a00b9

← previous block·next block →recent activity