← previous blocknext block →recent activity

Analyzing

Block #92,544,911

19 transactions · 17 stateful · 2026-08-02 17:11:26 UTC

Parallelism

68/100

Blocked

47%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #92,544,911  ·  19 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

0x547ab6de…28d1

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0x3270d9f8…099a

0x34b655…2a6f

6 touches
3 conflicts

0x6719a767…9d62

0x34b655…2a6f

6 touches
3 conflicts

0xa03c2a35…52e6

0x34b655…2a6f

6 touches
3 conflicts

0xa56e54d0…2d39

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 0x547ab6def1…e328d1

← previous block·next block →recent activity