← previous blocknext block →recent activity

Analyzing

Block #87,497,804

20 transactions · 17 stateful · 2026-07-13 13:56:11 UTC

Parallelism

80/100

Blocked

41%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,497,804  ·  20 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

0xc36fa358…24cb

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xbe2f0390…da0f

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x32dfa6a9…12f6

0x34b655…2a6f

6 touches
3 conflicts

0x963bd911…c7a4

0x34b655…2a6f

4 touches
1 conflict

0xa1002523…644f

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 0xc36fa35805…6f24cb

← previous block·next block →recent activity