← previous blocknext block →recent activity

Analyzing

Block #87,638,262

20 transactions · 18 stateful · 2026-07-14 05:36:22 UTC

Parallelism

35/100

Blocked

72%

Avg conflicts / tx

2.35

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #87,638,262  ·  20 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0xb5a3b1be…8122

0x34b655…2a6f

16 touches
28 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

14 touches
21 conflicts

0x5b145de0…367c

0xc8689a…ee79

10 touches
10 conflicts

0x2dfde2ed…8801

0x34b655…2a6f

10 touches
10 conflicts

0x49f75237…44f4

0x34b655…2a6f

10 touches
10 conflicts

0x8981596f…d14a

0x34b655…2a6f

10 touches
10 conflicts

0x9599eb41…b5d6

0x34b655…2a6f

10 touches
10 conflicts

0xcc6e2e88…6569

0x34b655…2a6f

10 touches
10 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

28 conflicts on slot 0xb5a3b1be7c…288122

← previous block·next block →recent activity