← previous blocknext block →recent activity

Analyzing

Block #87,661,160

17 transactions · 15 stateful · 2026-07-14 08:09:17 UTC

Parallelism

76/100

Blocked

53%

Avg conflicts / tx

0.59

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,661,160  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x59dccbd8…2bf6

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x3f7d8a09…362c

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x5a36d0c8…12e2

0x34b655…2a6f

4 touches
1 conflict

0x5a36d0c8…12e3

0x34b655…2a6f

4 touches
1 conflict

0x5c79a7db…b7aa

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 0x59dccbd857…c52bf6

← previous block·next block →recent activity