← previous blocknext block →recent activity

Analyzing

Block #91,101,646

20 transactions · 18 stateful · 2026-07-28 16:09:19 UTC

Parallelism

50/100

Blocked

56%

Avg conflicts / tx

1.85

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #91,101,646  ·  20 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xb9834665…e363

0x34b655…2a6f

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x87d938d7…dc5e

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0xd0d1276b…2725

0x34b655…2a6f

6 touches
3 conflicts

0x3d22c439…de6d

0x34b655…2a6f

6 touches
3 conflicts

0x7aaf17a2…3988

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

21 conflicts on slot 0xb983466539…cee363

← previous block·next block →recent activity