← previous blocknext block →recent activity

Analyzing

Block #87,623,865

22 transactions · 21 stateful · 2026-07-14 04:00:03 UTC

Parallelism

77/100

Blocked

38%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,623,865  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xf79df061…e005

0xe52b14…7230

10 touches
10 conflicts

0x99c46e97…c1b2

0x34b655…2a6f

6 touches
3 conflicts

0x07b116a4…6198

0x34b655…2a6f

4 touches
1 conflict

0x1041bcb3…4c7a

0x34b655…2a6f

4 touches
1 conflict

0x1487893e…4055

0x34b655…2a6f

4 touches
1 conflict

0x176771f9…c1a4

0x34b655…2a6f

4 touches
1 conflict

0x19e9a11b…e981

0x34b655…2a6f

4 touches
1 conflict

0x254b4113…6fd2

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: 0xe52b1424…bb7230

10 conflicts on slot 0xf79df061c7…91e005

← previous block·next block →recent activity