← previous blocknext block →recent activity

Analyzing

Block #90,706,401

9 transactions · 9 stateful · 2026-07-27 06:59:54 UTC

Parallelism

78/100

Blocked

22%

Avg conflicts / tx

0.22

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #90,706,401  ·  9 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

0x53d6f1c9…16c4

0x34b655…2a6f

4 touches
1 conflict

0xba69aad3…bca6

0x34b655…2a6f

4 touches
1 conflict

0x93b6fab0…09d6

0x34b655…2a6f

4 touches
1 conflict

0x2754c3f9…9863

0x34b655…2a6f

2 touches
0 conflicts

0x2d216d2e…da95

0x34b655…2a6f

2 touches
0 conflicts

0x52f7c71c…d0a6

0x34b655…2a6f

2 touches
0 conflicts

0x5e8223c2…c242

0x34b655…2a6f

2 touches
0 conflicts

0x66067e58…fbec

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

1 conflict on slot 0x53d6f1c94f…9016c4

← previous block·next block →recent activity