← previous blocknext block →recent activity

Analyzing

Block #90,224,045

17 transactions · 17 stateful · 2026-07-25 14:18:22 UTC

Parallelism

88/100

Blocked

35%

Avg conflicts / tx

0.35

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #90,224,045  ·  17 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

0x42041fec…bd86

0x754704…b603

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x0f2d78b1…7363

0x34b655…2a6f

4 touches
1 conflict

0x31b39922…1e66

0x34b655…2a6f

4 touches
1 conflict

0x4cb450ac…4047

0x34b655…2a6f

4 touches
1 conflict

0x66bdb4c2…7ea6

0x34b655…2a6f

4 touches
1 conflict

0x8eef368f…aa21

0x34b655…2a6f

4 touches
1 conflict

0xb03f96de…b58b

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: USDC (USDC)

1 conflict on slot 0x42041feca2…afbd86

← previous block·next block →recent activity