← previous blocknext block →recent activity

Analyzing

Block #96,837,403

20 transactions · 19 stateful · 2026-08-17 17:36:55 UTC

Parallelism

70/100

Blocked

42%

Avg conflicts / tx

1.45

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #96,837,403  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xac3e4969…39e9

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x4cabb80a…46bf

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xf9e23360…8ef7

0x34b655…2a6f

6 touches
3 conflicts

0xba9f9225…2ead

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

15 conflicts on slot 0xac3e4969cf…1739e9

← previous block·next block →recent activity