← previous blocknext block →recent activity

Analyzing

Block #86,487,393

26 transactions · 23 stateful · 2026-07-08 21:19:38 UTC

Parallelism

50/100

Blocked

57%

Avg conflicts / tx

2.54

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #86,487,393  ·  26 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

0x2011ff06…05aa

0x34b655…2a6f

14 touches
21 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

14 touches
21 conflicts

0x7ee6007b…fd68

0x34b655…2a6f

12 touches
15 conflicts

0xfaef08b1…0696

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x03fb27fd…0c06

0x34b655…2a6f

10 touches
10 conflicts

0x9f40a209…1193

0x34b655…2a6f

10 touches
10 conflicts

0xd99b3b64…1c95

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

21 conflicts on slot 0x2011ff062e…dd05aa

← previous block·next block →recent activity