← previous blocknext block →recent activity

Analyzing

Block #90,041,490

13 transactions · 12 stateful · 2026-07-24 22:55:18 UTC

Parallelism

69/100

Blocked

42%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,041,490  ·  13 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

0x5fdfa820…7b4b

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0xfac3092e…6559

0x34b655…2a6f

4 touches
1 conflict

0xb1c67a7d…b9b1

0x34b655…2a6f

2 touches
0 conflicts

0xb9b4eff6…c3ef

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 0x5fdfa820c5…2d7b4b

← previous block·next block →recent activity