← previous blocknext block →recent activity

Analyzing

Block #90,374,908

16 transactions · 16 stateful · 2026-07-26 03:04:50 UTC

Parallelism

69/100

Blocked

56%

Avg conflicts / tx

1.25

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,374,908  ·  16 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x2a2787a1…c9e1

0x34b655…2a6f

8 touches
6 conflicts

0x745952b2…d90c

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x31b39922…1e66

0x34b655…2a6f

4 touches
1 conflict

0x3ca268be…8865

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity