← previous blocknext block →recent activity

Analyzing

Block #96,180,985

19 transactions · 18 stateful · 2026-08-15 10:35:06 UTC

Parallelism

63/100

Blocked

61%

Avg conflicts / tx

1.58

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #96,180,985  ·  19 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

0xb3fb9fb5…64db

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x36890fff…f3d1

0x34b655…2a6f

6 touches
3 conflicts

0xaba6578d…bd48

0x34b655…2a6f

6 touches
3 conflicts

0x78b7945b…2113

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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