← previous blocknext block →recent activity

Analyzing

Block #92,188,457

20 transactions · 19 stateful · 2026-08-01 11:18:45 UTC

Parallelism

80/100

Blocked

37%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #92,188,457  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x4368104f…fa86

0x7b9256…1fb2

8 touches
6 conflicts

0x4368104f…fa89

0x7b9256…1fb2

8 touches
6 conflicts

0xbbc8a4c0…7f17

0x7b9256…1fb2

8 touches
6 conflicts

0xbbc8a4c0…7f18

0x7b9256…1fb2

8 touches
6 conflicts

0x177211e2…1c2d

0x754704…b603

8 touches
6 conflicts

0xe1f61186…e2f8

0x754704…b603

8 touches
6 conflicts

0x00000000…0006

0x7b9256…1fb2

8 touches
6 conflicts

0x4368104f…fa85

0x7b9256…1fb2

8 touches
6 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

6 conflicts on slot 0x4368104fd9…30fa86

← previous block·next block →recent activity