← previous blocknext block →recent activity

Analyzing

Block #92,859,265

24 transactions · 19 stateful · 2026-08-03 19:34:00 UTC

Parallelism

75/100

Blocked

42%

Avg conflicts / tx

0.71

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #92,859,265  ·  24 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

0x4acbdbcf…a8c6

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0x737acb78…fce8

0x34b655…2a6f

10 touches
10 conflicts

0x840d3ab7…c8c4

0x34b655…2a6f

6 touches
3 conflicts

0x4e8c4408…d37a

0x34b655…2a6f

4 touches
1 conflict

0x4e8c4408…d37b

0x34b655…2a6f

4 touches
1 conflict

0x67b7c4b9…179b

0x34b655…2a6f

4 touches
1 conflict

0x0d488000…3831

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

10 conflicts on slot 0x4acbdbcf7f…d0a8c6

← previous block·next block →recent activity