← previous blocknext block →recent activity

Analyzing

Block #91,188,647

15 transactions · 14 stateful · 2026-07-28 23:26:58 UTC

Parallelism

80/100

Blocked

43%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #91,188,647  ·  15 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

0x159cff26…7665

0x34b655…2a6f

4 touches
1 conflict

0xa1ff0729…0146

0xa6afd3…d132

4 touches
1 conflict

0x890a1db9…1712

0xa6afd3…d132

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x00000000…004c

0x80c745…7210

4 touches
1 conflict

0x00000000…004b

0x80c745…7210

4 touches
1 conflict

0x00000000…0002

0x48cba2…b48b

4 touches
1 conflict

0xb1b58b33…874f

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 0x159cff262c…e57665

← previous block·next block →recent activity