← previous blocknext block →recent activity

Analyzing

Block #91,255,246

21 transactions · 19 stateful · 2026-07-29 05:02:05 UTC

Parallelism

71/100

Blocked

37%

Avg conflicts / tx

0.81

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #91,255,246  ·  21 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x34a1ee7e…fb20

0x34b655…2a6f

6 touches
3 conflicts

0x53cccb07…d7f0

0x34b655…2a6f

4 touches
1 conflict

0x5af098c7…4806

0x34b655…2a6f

4 touches
1 conflict

0x5af098c7…4807

0x34b655…2a6f

4 touches
1 conflict

0x6c26d635…1bbf

0x34b655…2a6f

4 touches
1 conflict

0x7aad02c6…b979

0x34b655…2a6f

4 touches
1 conflict

0x9807e413…7362

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity