← previous blocknext block →recent activity

Analyzing

Block #92,634,193

11 transactions · 11 stateful · 2026-08-03 00:40:29 UTC

Parallelism

82/100

Blocked

27%

Avg conflicts / tx

0.36

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #92,634,193  ·  11 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

0x05ca4d57…2eed

0x34b655…2a6f

4 touches
1 conflict

0xa870b15b…9701

0xa6afd3…d132

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xc0312d74…5e25

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xbbeac3b7…c14b

0x34b655…2a6f

4 touches
1 conflict

0x86977b3d…a9c4

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

1 conflict on slot 0x05ca4d57c3…062eed

← previous block·next block →recent activity