← previous blocknext block →recent activity

Analyzing

Block #91,970,102

19 transactions · 19 stateful · 2026-07-31 17:00:33 UTC

Parallelism

68/100

Blocked

37%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #91,970,102  ·  19 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xe9348870…b66a

0x34b655…2a6f

4 touches
1 conflict

0xd1b40f29…9b9d

0x34b655…2a6f

4 touches
1 conflict

0x02991b41…19e6

0x34b655…2a6f

4 touches
1 conflict

0x8a5ced1c…3b29

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0xe6ac7795…7f57

0xd32edf…ff58

3 touches
1 conflict

0x7f4a8466…f2cc

0x2b46c0…1669

2 touches
0 conflicts

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity