← previous blocknext block →recent activity

Analyzing

Block #92,697,198

16 transactions · 15 stateful · 2026-08-03 05:58:17 UTC

Parallelism

63/100

Blocked

53%

Avg conflicts / tx

0.94

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #92,697,198  ·  16 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

0xc5031114…58ac

0x34b655…2a6f

8 touches
6 conflicts

0x56153262…21ce

0x34b655…2a6f

6 touches
3 conflicts

0xa948bd93…b5dd

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0018

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0028

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21bf

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x34a1ee7e…fb20

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: Perpl

6 conflicts on slot 0xc503111436…e358ac

← previous block·next block →recent activity