← previous blocknext block →recent activity

Analyzing

Block #92,065,484

20 transactions · 19 stateful · 2026-08-01 01:00:17 UTC

Parallelism

60/100

Blocked

47%

Avg conflicts / tx

1.5

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #92,065,484  ·  20 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xc02b22af…d5fa

0x7b9256…1fb2

16 touches
28 conflicts

0xe1f61186…e2f8

0x754704…b603

16 touches
28 conflicts

0x00000000…0006

0x7b9256…1fb2

16 touches
28 conflicts

0x246e476d…8cd1

0x7b9256…1fb2

16 touches
28 conflicts

0x246e476d…8cd2

0x7b9256…1fb2

16 touches
28 conflicts

0x177211e2…1c2d

0x754704…b603

16 touches
28 conflicts

0xc02b22af…d5f6

0x7b9256…1fb2

16 touches
28 conflicts

0xc02b22af…d5f7

0x7b9256…1fb2

16 touches
28 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: 0x7b9256fd…e21fb2

28 conflicts on slot 0xc02b22afe3…07d5fa

← previous block·next block →recent activity