← previous blocknext block →recent activity

Analyzing

Block #92,177,078

20 transactions · 20 stateful · 2026-08-01 10:21:32 UTC

Parallelism

65/100

Blocked

45%

Avg conflicts / tx

1.25

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #92,177,078  ·  20 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

0x29921d44…4167

0x7b9256…1fb2

14 touches
21 conflicts

0x29921d44…4168

0x7b9256…1fb2

14 touches
21 conflicts

0x29921d44…416b

0x7b9256…1fb2

14 touches
21 conflicts

0xcc806aa8…6908

0x7b9256…1fb2

14 touches
21 conflicts

0xcc806aa8…6909

0x7b9256…1fb2

14 touches
21 conflicts

0x177211e2…1c2d

0x754704…b603

14 touches
21 conflicts

0xe1f61186…e2f8

0x754704…b603

14 touches
21 conflicts

0x00000000…0006

0x7b9256…1fb2

14 touches
21 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

21 conflicts on slot 0x29921d447d…b54167

← previous block·next block →recent activity