← previous blocknext block →recent activity

Analyzing

Block #91,540,064

15 transactions · 14 stateful · 2026-07-30 04:57:13 UTC

Parallelism

67/100

Blocked

50%

Avg conflicts / tx

1.13

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,540,064  ·  15 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xa953856d…3bef

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…004b

0x80c745…7210

6 touches
3 conflicts

0x758a0dd5…0f46

0x34b655…2a6f

4 touches
1 conflict

0x8ddcac26…5c5a

0x34b655…2a6f

4 touches
1 conflict

0x94de4d05…ad01

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity