← previous blocknext block →recent activity

Analyzing

Block #96,157,644

17 transactions · 15 stateful · 2026-08-15 08:37:42 UTC

Parallelism

59/100

Blocked

67%

Avg conflicts / tx

1.29

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #96,157,644  ·  17 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

0x4c188934…158e

0x34b655…2a6f

12 touches
15 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x62bd1793…0097

0x34b655…2a6f

6 touches
3 conflicts

0x24223eb9…13ba

0x34b655…2a6f

4 touches
1 conflict

0x42c27cea…b5f3

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0x02679875…8d2f

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 0x4c18893450…c5158e

← previous block·next block →recent activity