← previous blocknext block →recent activity

Analyzing

Block #87,705,485

28 transactions · 21 stateful · 2026-07-14 13:05:49 UTC

Parallelism

79/100

Blocked

38%

Avg conflicts / tx

0.43

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,705,485  ·  28 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x8fe37a3f…4c89

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x3de775b2…319b

0xa6afd3…d132

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x67905f6e…02a1

0x34b655…2a6f

4 touches
1 conflict

0x6b436af2…3c05

0x34b655…2a6f

4 touches
1 conflict

0x7837c02d…0965

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 0x8fe37a3f4a…bf4c89

← previous block·next block →recent activity