← previous blocknext block →recent activity

Analyzing

Block #92,769,502

18 transactions · 17 stateful · 2026-08-03 12:02:14 UTC

Parallelism

89/100

Blocked

12%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #92,769,502  ·  18 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

0x4f6adebf…e492

0x34b655…2a6f

4 touches
1 conflict

0x213a54fa…c85f

0x34b655…2a6f

4 touches
1 conflict

0x74fd0a9b…3aaa

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x900ed82d…e53a

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x2af994dd…f90d

0x34b655…2a6f

2 touches
0 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: Perpl

1 conflict on slot 0x4f6adebfc0…a7e492

← previous block·next block →recent activity