← previous blocknext block →recent activity

Analyzing

Block #87,919,015

31 transactions · 20 stateful · 2026-07-15 12:54:16 UTC

Parallelism

77/100

Blocked

45%

Avg conflicts / tx

0.52

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,919,015  ·  31 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

0x4f1ad4b4…e00a

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x4b2b1640…1bb8

0x34b655…2a6f

6 touches
3 conflicts

0x2368f602…b37a

0xd32edf…ff58

5 touches
3 conflicts

0x33bc42f7…45b9

0x34b655…2a6f

4 touches
1 conflict

0x346e6e22…8deb

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 0x4f1ad4b4ec…b9e00a

← previous block·next block →recent activity