← previous blocknext block →recent activity

Analyzing

Block #92,110,718

17 transactions · 15 stateful · 2026-08-01 04:47:45 UTC

Parallelism

71/100

Blocked

53%

Avg conflicts / tx

0.94

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #92,110,718  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xda48994d…7b37

0x7b9256…1fb2

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

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

0x6fa6d196…ac13

0x7b9256…1fb2

8 touches
6 conflicts

0x6fa6d196…ac14

0x7b9256…1fb2

8 touches
6 conflicts

0xda48994d…7b33

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 0xda48994db4…f27b37

← previous block·next block →recent activity