← previous blocknext block →recent activity

Analyzing

Block #87,902,534

18 transactions · 17 stateful · 2026-07-15 11:04:04 UTC

Parallelism

78/100

Blocked

41%

Avg conflicts / tx

0.61

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,902,534  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x9f83113a…dcd8

0x34b655…2a6f

8 touches
6 conflicts

0x347796c5…bfc0

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0001

0xc1ff9f…b0fc

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0xdf06241e…adf9

0x34b655…2a6f

4 touches
1 conflict

0x2bfb71b5…3a04

0x34b655…2a6f

4 touches
1 conflict

0x2bfb71b5…3a05

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

6 conflicts on slot 0x9f83113ae0…0edcd8

← previous block·next block →recent activity