← previous blocknext block →recent activity

Analyzing

Block #86,925,504

22 transactions · 22 stateful · 2026-07-10 22:09:54 UTC

Parallelism

45/100

Blocked

50%

Avg conflicts / tx

2.32

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #86,925,504  ·  22 txs across 12 waves  ·  depth 12
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

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

0xa08f40b2…9a93

0x34b655…2a6f

18 touches
36 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x92385428…6941

0x34b655…2a6f

10 touches
10 conflicts

0xa248a5dd…4a69

0x34b655…2a6f

10 touches
10 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x01a056f8…64e4

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

36 conflicts on slot 0xa08f40b255…099a93

← previous block·next block →recent activity