← previous blocknext block →recent activity

Analyzing

Block #92,530,752

14 transactions · 14 stateful · 2026-08-02 16:00:14 UTC

Parallelism

57/100

Blocked

64%

Avg conflicts / tx

1.43

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #92,530,752  ·  14 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xb18e1e9d…2705

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x29c1a140…099f

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0x2b54cadb…4425

0xd18b7e…414b

6 touches
3 conflicts

0x948836ff…59ab

0x34b655…2a6f

6 touches
3 conflicts

0xd66696e0…0842

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

15 conflicts on slot 0xb18e1e9d43…032705

← previous block·next block →recent activity