← previous blocknext block →recent activity

Analyzing

Block #84,359,131

32 transactions · 21 stateful · 2026-06-29 00:46:32 UTC

Parallelism

72/100

Blocked

43%

Avg conflicts / tx

0.75

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #84,359,131  ·  32 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

0xfd4e2262…cd8c

0x34b655…2a6f

10 touches
10 conflicts

0x5a5dd7b4…fba4

0x34b655…2a6f

8 touches
6 conflicts

0x2e86dd1e…dc3e

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xe99ebc4d…22f9

0x34b655…2a6f

6 touches
3 conflicts

0x3e2319d1…b068

0x34b655…2a6f

6 touches
3 conflicts

0x793aa64d…b09c

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