← previous blocknext block →recent activity

Analyzing

Block #91,248,117

26 transactions · 21 stateful · 2026-07-29 04:26:10 UTC

Parallelism

77/100

Blocked

38%

Avg conflicts / tx

0.54

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #91,248,117  ·  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

0xa20a130c…5d59

0x34b655…2a6f

8 touches
6 conflicts

0xe10dad88…8549

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x805d08cf…3cfc

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0x48cba2…b48b

4 touches
1 conflict

0x1e81ea5f…2510

0x34b655…2a6f

4 touches
1 conflict

0x350e5d8a…601f

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

6 conflicts on slot 0xa20a130ca6…b85d59

← previous block·next block →recent activity