← previous blocknext block →recent activity

Analyzing

Block #91,763,347

26 transactions · 24 stateful · 2026-07-30 23:40:23 UTC

Parallelism

77/100

Blocked

38%

Avg conflicts / tx

0.65

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #91,763,347  ·  26 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

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0x5655f5c3…6b75

0x34b655…2a6f

8 touches
6 conflicts

0xc6b604e6…5152

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x24551912…0fa7

0x34b655…2a6f

6 touches
3 conflicts

0x8c1f604e…8522

0x34b655…2a6f

4 touches
1 conflict

0x9ce12847…cbb2

0x34b655…2a6f

4 touches
1 conflict

0xa3f095f5…bd87

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 0x482471adbb…39122f

← previous block·next block →recent activity