← previous blocknext block →recent activity

Analyzing

Block #96,046,079

21 transactions · 19 stateful · 2026-08-14 23:16:33 UTC

Parallelism

67/100

Blocked

47%

Avg conflicts / tx

1.43

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #96,046,079  ·  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

0xf5ea108a…dbf6

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x31616f97…1acc

0x34b655…2a6f

6 touches
3 conflicts

0x7fe44102…0623

0x34b655…2a6f

6 touches
3 conflicts

0x8f63f383…6eda

0x34b655…2a6f

4 touches
1 conflict

0x96bca57d…4d43

0x34b655…2a6f

4 touches
1 conflict

0x9a8af3c2…e4ae

0x34b655…2a6f

4 touches
1 conflict

0xb3fb9fb5…64db

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

21 conflicts on slot 0xf5ea108a6a…e5dbf6

← previous block·next block →recent activity