← previous blocknext block →recent activity

Analyzing

Block #92,297,014

23 transactions · 21 stateful · 2026-08-01 20:24:43 UTC

Parallelism

74/100

Blocked

38%

Avg conflicts / tx

0.83

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #92,297,014  ·  23 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

0x0d58ef33…fba5

0x7b9256…1fb2

12 touches
15 conflicts

0x177211e2…1c2d

0x754704…b603

12 touches
15 conflicts

0xe1f61186…e2f8

0x754704…b603

12 touches
15 conflicts

0x00000000…0006

0x7b9256…1fb2

12 touches
15 conflicts

0x0d58ef33…fba4

0x7b9256…1fb2

12 touches
15 conflicts

0x69e6a72f…30d8

0x7b9256…1fb2

12 touches
15 conflicts

0x69e6a72f…30d5

0x7b9256…1fb2

12 touches
15 conflicts

0x69e6a72f…30d4

0x7b9256…1fb2

12 touches
15 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

15 conflicts on slot 0x0d58ef33f5…d8fba5

← previous block·next block →recent activity