← previous blocknext block →recent activity

Analyzing

Block #87,357,558

25 transactions · 23 stateful · 2026-07-12 22:18:15 UTC

Parallelism

64/100

Blocked

57%

Avg conflicts / tx

1.68

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,357,558  ·  25 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xfaef08b1…0696

0x34b655…2a6f

10 touches
10 conflicts

0x89c7ec3b…85ba

0x34b655…2a6f

8 touches
6 conflicts

0x93b6fab0…09d6

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xc9dce17a…a1a1

0x34b655…2a6f

8 touches
6 conflicts

0x400fb569…d594

0x34b655…2a6f

6 touches
3 conflicts

0x63c900f4…2600

0x34b655…2a6f

6 touches
3 conflicts

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity