← previous blocknext block →recent activity

Analyzing

Block #90,241,152

19 transactions · 18 stateful · 2026-07-25 15:44:36 UTC

Parallelism

84/100

Blocked

33%

Avg conflicts / tx

0.58

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #90,241,152  ·  19 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x54a7b790…c2c6

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x42041fec…bd86

0x754704…b603

6 touches
3 conflicts

0x2d3930d3…c9b8

0x34b655…2a6f

4 touches
1 conflict

0x31b39922…1e66

0x34b655…2a6f

4 touches
1 conflict

0x3fcb7de0…0bb0

0x34b655…2a6f

4 touches
1 conflict

0x57b3b97e…7ca7

0x34b655…2a6f

4 touches
1 conflict

0x65487580…b5eb

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0x54a7b7904d…e3c2c6

← previous block·next block →recent activity