← previous blocknext block →recent activity

Analyzing

Block #92,690,287

7 transactions · 7 stateful · 2026-08-03 05:23:30 UTC

Parallelism

57/100

Blocked

29%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #92,690,287  ·  7 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xda46a376…f6a6

0x34b655…2a6f

6 touches
3 conflicts

0xfbd04d13…95f3

0x34b655…2a6f

4 touches
1 conflict

0x268d9251…1c7f

0x34b655…2a6f

4 touches
1 conflict

0x42b10c57…3ee7

0x34b655…2a6f

4 touches
1 conflict

0x6d02e779…a7f1

0x34b655…2a6f

4 touches
1 conflict

0x939bee45…dce6

0x34b655…2a6f

4 touches
1 conflict

0xa03c2a35…52e6

0x34b655…2a6f

4 touches
1 conflict

0xb4df7a5b…b329

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

3 conflicts on slot 0xda46a376d7…59f6a6

← previous block·next block →recent activity