← previous blocknext block →recent activity

Analyzing

Block #90,385,100

13 transactions · 13 stateful · 2026-07-26 03:57:14 UTC

Parallelism

85/100

Blocked

23%

Avg conflicts / tx

0.23

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #90,385,100  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x742436a7…c4d4

0x34b655…2a6f

4 touches
1 conflict

0x745952b2…d90c

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x588380ee…0a5c

0x34b655…2a6f

4 touches
1 conflict

0x5e8ddd73…4dfb

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

1 conflict on slot 0x742436a7e5…69c4d4

← previous block·next block →recent activity