← previous blocknext block →recent activity

Analyzing

Block #90,719,100

8 transactions · 7 stateful · 2026-07-27 08:03:47 UTC

Parallelism

75/100

Blocked

29%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #90,719,100  ·  8 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

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xe52a5e77…41a4

0x34b655…2a6f

4 touches
1 conflict

0x17fff7d7…7b9a

0x34b655…2a6f

2 touches
0 conflicts

0x19c056c4…8ee3

0x34b655…2a6f

2 touches
0 conflicts

0x34a1ee7e…fb20

0x34b655…2a6f

2 touches
0 conflicts

0x3ca268be…8865

0x34b655…2a6f

2 touches
0 conflicts

0x4bcd2b7c…a670

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 0xc824469a90…af6425

← previous block·next block →recent activity