← previous blocknext block →recent activity

Analyzing

Block #96,600,341

17 transactions · 13 stateful · 2026-08-16 21:44:35 UTC

Parallelism

88/100

Blocked

23%

Avg conflicts / tx

0.24

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #96,600,341  ·  17 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0x7507c98f…bf65

0x34b655…2a6f

4 touches
1 conflict

0xcea40325…6b39

0x34b655…2a6f

4 touches
1 conflict

0x784eaad2…d176

0x34b655…2a6f

4 touches
1 conflict

0x3cf50d44…961b

0x34b655…2a6f

4 touches
1 conflict

0xf90c6521…d8f0

0x34b655…2a6f

4 touches
1 conflict

0xb07f01e3…0ad4

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

1 conflict on slot 0x482471adbb…39122f

← previous block·next block →recent activity