← previous blocknext block →recent activity

Analyzing

Block #90,296,741

21 transactions · 20 stateful · 2026-07-25 20:25:45 UTC

Parallelism

76/100

Blocked

40%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,296,741  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x00000000…0006

0x0a2fbf…29b1

8 touches
6 conflicts

0xa3f9210f…8173

0x0a2fbf…29b1

8 touches
6 conflicts

0xa3f9210f…8174

0x0a2fbf…29b1

8 touches
6 conflicts

0xda986c60…8625

0x0a2fbf…29b1

8 touches
6 conflicts

0xda986c60…8626

0x0a2fbf…29b1

8 touches
6 conflicts

0xda986c60…8629

0x0a2fbf…29b1

8 touches
6 conflicts

0x00000000…0005

0x370e2e…63b4

8 touches
6 conflicts

0x1bff683e…7ecb

0x754704…b603

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: 0x0a2fbf2d…f729b1

6 conflicts on slot 0x0000000000…000006

← previous block·next block →recent activity