← previous blocknext block →recent activity

Analyzing

Block #90,515,640

18 transactions · 17 stateful · 2026-07-26 15:00:16 UTC

Parallelism

78/100

Blocked

35%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,515,640  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x6847107a…f468

0xa6afd3…d132

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x226ae29a…2612

0x34b655…2a6f

4 touches
1 conflict

0x2f358e74…1022

0x34b655…2a6f

4 touches
1 conflict

0x5f5a0edf…ebcc

0x34b655…2a6f

4 touches
1 conflict

0x7c09c53e…64b4

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

3 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity