← previous blocknext block →recent activity

Analyzing

Block #92,556,213

16 transactions · 16 stateful · 2026-08-02 18:08:16 UTC

Parallelism

88/100

Blocked

19%

Avg conflicts / tx

0.19

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #92,556,213  ·  16 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

0x7e1faa73…bfbf

0x34b655…2a6f

4 touches
1 conflict

0x805d08cf…3cfc

0x34b655…2a6f

4 touches
1 conflict

0xc0ab38cc…600c

0x34b655…2a6f

4 touches
1 conflict

0xd4b0bafb…80ac

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

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 0x7e1faa73db…84bfbf

← previous block·next block →recent activity