← previous blocknext block →recent activity

Analyzing

Block #87,594,847

21 transactions · 18 stateful · 2026-07-14 00:46:01 UTC

Parallelism

81/100

Blocked

28%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,594,847  ·  21 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

0x756ad195…36a3

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x2130a548…c1de

0x34b655…2a6f

4 touches
1 conflict

0x3be33cca…0fff

0x34b655…2a6f

4 touches
1 conflict

0x3be33cca…1000

0x34b655…2a6f

4 touches
1 conflict

0x46fdb575…fe2d

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0x7c2c8fb9…319a

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 0x756ad19507…7536a3

← previous block·next block →recent activity