← previous blocknext block →recent activity

Analyzing

Block #92,310,825

19 transactions · 19 stateful · 2026-08-01 21:34:11 UTC

Parallelism

63/100

Blocked

53%

Avg conflicts / tx

1.21

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #92,310,825  ·  19 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x7a4d6a5a…4559

0x7b9256…1fb2

10 touches
10 conflicts

0x7a4d6a5a…455c

0x7b9256…1fb2

10 touches
10 conflicts

0x177211e2…1c2d

0x754704…b603

10 touches
10 conflicts

0xe1f61186…e2f8

0x754704…b603

10 touches
10 conflicts

0x00000000…0006

0x7b9256…1fb2

10 touches
10 conflicts

0x67c1ee46…7bb9

0x7b9256…1fb2

10 touches
10 conflicts

0x67c1ee46…7bba

0x7b9256…1fb2

10 touches
10 conflicts

0x7a4d6a5a…4558

0x7b9256…1fb2

10 touches
10 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

10 conflicts on slot 0x7a4d6a5a6c…544559

← previous block·next block →recent activity