← previous blocknext block →recent activity

Analyzing

Block #92,807,306

19 transactions · 17 stateful · 2026-08-03 15:12:28 UTC

Parallelism

74/100

Blocked

47%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #92,807,306  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x0f2d78b1…7363

0x34b655…2a6f

8 touches
6 conflicts

0xc836c7e9…b544

0x34b655…2a6f

6 touches
3 conflicts

0xda27c764…7fab

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…001b

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002b

0x1b6862…e19c

4 touches
1 conflict

0x0a85a226…83bd

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x0c21cc22…f749

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

6 conflicts on slot 0x0f2d78b1bb…5e7363

← previous block·next block →recent activity