← previous blocknext block →recent activity

Analyzing

Block #87,498,214

22 transactions · 20 stateful · 2026-07-13 13:58:56 UTC

Parallelism

73/100

Blocked

40%

Avg conflicts / tx

0.68

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,498,214  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x63ad92a0…7912

0x34b655…2a6f

10 touches
10 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xc36fa358…24cb

0x34b655…2a6f

8 touches
6 conflicts

0x53f393fa…00b9

0x34b655…2a6f

6 touches
3 conflicts

0x46b3589e…f54b

0x34b655…2a6f

4 touches
1 conflict

0x61e7b277…fee7

0x34b655…2a6f

4 touches
1 conflict

0x62222abd…e410

0x34b655…2a6f

4 touches
1 conflict

0x68bec689…fccd

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

10 conflicts on slot 0x63ad92a0b2…057912

← previous block·next block →recent activity