← previous blocknext block →recent activity

Analyzing

Block #92,967,732

14 transactions · 13 stateful · 2026-08-04 04:39:42 UTC

Parallelism

86/100

Blocked

31%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #92,967,732  ·  14 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

0xeb5d573d…ab76

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721c

0x34b655…2a6f

4 touches
1 conflict

0xc7f6eab9…9e9f

0x34b655…2a6f

4 touches
1 conflict

0xe26c4e53…94c2

0x34b655…2a6f

4 touches
1 conflict

0xe26c4e53…94c3

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x107b89e4…470d

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 0xeb5d573dbe…35ab76

← previous block·next block →recent activity