← previous blocknext block →recent activity

Analyzing

Block #86,682,454

30 transactions · 27 stateful · 2026-07-09 19:05:43 UTC

Parallelism

57/100

Blocked

52%

Avg conflicts / tx

1.33

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #86,682,454  ·  30 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xfaef08b1…0696

0x34b655…2a6f

10 touches
10 conflicts

0x1a5d321d…a474

0x34b655…2a6f

6 touches
3 conflicts

0x4dab31d4…61b0

0x34b655…2a6f

6 touches
3 conflicts

0x3ca268be…8865

0x34b655…2a6f

6 touches
3 conflicts

0xa08f40b2…9a93

0x34b655…2a6f

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xc6dcef4f…39dd

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity