← previous blocknext block →recent activity

Analyzing

Block #87,421,644

28 transactions · 22 stateful · 2026-07-13 05:26:56 UTC

Parallelism

89/100

Blocked

27%

Avg conflicts / tx

0.39

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,421,644  ·  28 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

0xd69f26b4…c204

0x2a68ba…90c5

6 touches
3 conflicts

0xc36fa358…24cb

0x34b655…2a6f

6 touches
3 conflicts

0xea4b86ec…900f

0x34b655…2a6f

6 touches
3 conflicts

0xffc2f21e…b393

0x34b655…2a6f

6 touches
3 conflicts

0x96217eb8…5b7a

0x851145…3f07

6 touches
3 conflicts

0x244a878b…48a7

0x34b655…2a6f

4 touches
1 conflict

0x36b3b55b…473a

0x34b655…2a6f

4 touches
1 conflict

0x76196ad0…ce0c

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: Kuru Exchange: MarginAccount

3 conflicts on slot 0xd69f26b400…cdc204

← previous block·next block →recent activity