← previous blocknext block →recent activity

Analyzing

Block #87,169,449

15 transactions · 13 stateful · 2026-07-12 01:19:33 UTC

Parallelism

80/100

Blocked

31%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,169,449  ·  15 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xfbc00033…0f94

0x34b655…2a6f

4 touches
1 conflict

0x18e86f02…fa98

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x8a5d4f3f…d7b1

0x34b655…2a6f

4 touches
1 conflict

0xafb6ece6…53ba

0x34b655…2a6f

4 touches
1 conflict

0xbb520828…94c0

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity