← previous blocknext block →recent activity

Analyzing

Block #87,870,796

23 transactions · 21 stateful · 2026-07-15 07:31:45 UTC

Parallelism

83/100

Blocked

33%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,870,796  ·  23 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

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x72880226…1435

0x34b655…2a6f

6 touches
3 conflicts

0x8981596f…d14a

0x34b655…2a6f

4 touches
1 conflict

0x8d4a873e…1ada

0x34b655…2a6f

4 touches
1 conflict

0xa279b18d…63bc

0x34b655…2a6f

4 touches
1 conflict

0xc4cc0421…c4de

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity