← previous blocknext block →recent activity

Analyzing

Block #91,088,195

18 transactions · 18 stateful · 2026-07-28 15:01:37 UTC

Parallelism

61/100

Blocked

50%

Avg conflicts / tx

1.39

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #91,088,195  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x00000000…000b

0x90c374…be45

14 touches
21 conflicts

0x00000000…000a

0x90c374…be45

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x7aad02c6…b979

0x34b655…2a6f

4 touches
1 conflict

0x4560e5a8…b741

0x34b655…2a6f

4 touches
1 conflict

0x98834cc0…6c23

0x34b655…2a6f

4 touches
1 conflict

0xb5cddf91…0abf

0x34b655…2a6f

4 touches
1 conflict

0xd9a771df…a27b

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: 0x90c3747c…0ebe45

21 conflicts on slot 0x0000000000…00000b

← previous block·next block →recent activity