← previous blocknext block →recent activity

Analyzing

Block #87,870,384

16 transactions · 14 stateful · 2026-07-15 07:28:59 UTC

Parallelism

50/100

Blocked

64%

Avg conflicts / tx

1

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,870,384  ·  16 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xfcb6731c…b151

0x34b655…2a6f

6 touches
3 conflicts

0x2c390858…b1ed

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x50e84e6c…287f

0x34b655…2a6f

4 touches
1 conflict

0x6323c5ea…ce8a

0x34b655…2a6f

4 touches
1 conflict

0x64aaadbf…f9f3

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 0xfcb6731c4b…b9b151

← previous block·next block →recent activity