← previous blocknext block →recent activity

Analyzing

Block #87,350,126

16 transactions · 15 stateful · 2026-07-12 21:28:34 UTC

Parallelism

69/100

Blocked

47%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,350,126  ·  16 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x756913cf…e7bd

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xb0e974c4…b84d

0x34b655…2a6f

4 touches
1 conflict

0xb2f43a96…c350

0x34b655…2a6f

4 touches
1 conflict

0xc36fa358…24cb

0x34b655…2a6f

4 touches
1 conflict

0xd3ef5630…0de9

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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

3 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity