← previous blocknext block →recent activity

Analyzing

Block #87,712,088

25 transactions · 24 stateful · 2026-07-14 13:50:00 UTC

Parallelism

64/100

Blocked

46%

Avg conflicts / tx

1.16

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,712,088  ·  25 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xe5bb3628…e5f1

0x34b655…2a6f

10 touches
10 conflicts

0xa6389d47…9a28

0x34b655…2a6f

10 touches
10 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

10 touches
10 conflicts

0x7aad02c6…b979

0x34b655…2a6f

6 touches
3 conflicts

0x74fd0a9b…3aaa

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xbf78ee7f…e7fd

0x34b655…2a6f

4 touches
1 conflict

0xc0b9bd73…7f1c

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

10 conflicts on slot 0xe5bb3628b5…71e5f1

← previous block·next block →recent activity