← previous blocknext block →recent activity

Analyzing

Block #90,290,128

14 transactions · 13 stateful · 2026-07-25 19:52:07 UTC

Parallelism

79/100

Blocked

15%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #90,290,128  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x66bdb4c2…7ea6

0x34b655…2a6f

6 touches
3 conflicts

0x9b68408a…e609

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6426

0x34b655…2a6f

4 touches
1 conflict

0xab0760c4…4cfd

0x34b655…2a6f

4 touches
1 conflict

0x0431e51f…6f91

0x34b655…2a6f

4 touches
1 conflict

0x823a3658…acf6

0x34b655…2a6f

2 touches
0 conflicts

0x8e507257…71c1

0x34b655…2a6f

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

3 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity