← previous blocknext block →recent activity

Analyzing

Block #92,790,328

21 transactions · 20 stateful · 2026-08-03 13:47:02 UTC

Parallelism

71/100

Blocked

40%

Avg conflicts / tx

0.67

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #92,790,328  ·  21 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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x0f6aef87…8137

0x34b655…2a6f

4 touches
1 conflict

0x21605a79…d719

0x34b655…2a6f

4 touches
1 conflict

0x31616f97…1acc

0x34b655…2a6f

4 touches
1 conflict

0xee3b1b53…77dd

0xa6afd3…d132

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xf3d10975…0d07

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 0xca841faae5…71486a

← previous block·next block →recent activity