← previous blocknext block →recent activity

Analyzing

Block #92,482,313

13 transactions · 13 stateful · 2026-08-02 11:56:38 UTC

Parallelism

85/100

Blocked

23%

Avg conflicts / tx

0.23

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #92,482,313  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x2b54cadb…4425

0xd18b7e…414b

4 touches
1 conflict

0x540e42f5…19e1

0x34b655…2a6f

4 touches
1 conflict

0x56b4b003…a9f5

0x34b655…2a6f

4 touches
1 conflict

0x56b4b003…a9f6

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xe4636320…f407

0x34b655…2a6f

4 touches
1 conflict

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: Coinbase Wrapped BTC (cbBTC)

1 conflict on slot 0x2b54cadb82…7c4425

← previous block·next block →recent activity