← previous blocknext block →recent activity

Analyzing

Block #90,892,905

21 transactions · 20 stateful · 2026-07-27 22:38:16 UTC

Parallelism

43/100

Blocked

60%

Avg conflicts / tx

2.86

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #90,892,905  ·  21 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

22 touches
55 conflicts

0x482471ad…122f

0x34b655…2a6f

18 touches
36 conflicts

0x11e24c69…e70d

0x34b655…2a6f

12 touches
15 conflicts

0xa279b18d…63bc

0x34b655…2a6f

10 touches
10 conflicts

0xac8a5059…fd42

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0xd66696e0…0842

0x34b655…2a6f

8 touches
6 conflicts

0x31b39922…1e66

0x34b655…2a6f

8 touches
6 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

55 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity