← previous blocknext block →recent activity

Analyzing

Block #89,404,184

18 transactions · 18 stateful · 2026-07-22 10:28:00 UTC

Parallelism

89/100

Blocked

17%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #89,404,184  ·  18 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

0x9cf61590…ad8c

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xffc2f21e…b393

0x34b655…2a6f

4 touches
1 conflict

0x013a6b08…d120

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0x2b7950c1…2342

0x34b655…2a6f

4 touches
1 conflict

0x3d4c0233…20a5

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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

1 conflict on slot 0x9cf615906f…4ead8c

← previous block·next block →recent activity