← previous blocknext block →recent activity

Analyzing

Block #90,536,734

26 transactions · 24 stateful · 2026-07-26 16:46:22 UTC

Parallelism

73/100

Blocked

67%

Avg conflicts / tx

1.31

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #90,536,734  ·  26 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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…0002

0x48cba2…b48b

14 touches
21 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x9ff176a9…152e

0x065c9d…c394

4 touches
1 conflict

0x2dbecd73…cee1

0x34b655…2a6f

4 touches
1 conflict

0x4cabb80a…46bf

0x34b655…2a6f

4 touches
1 conflict

0x5502e1cc…3910

0x34b655…2a6f

4 touches
1 conflict

0x596ecf44…fbc2

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: 0x48cba278…e2b48b

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity