← previous blocknext block →recent activity

Analyzing

Block #87,262,880

18 transactions · 16 stateful · 2026-07-12 11:45:14 UTC

Parallelism

78/100

Blocked

50%

Avg conflicts / tx

0.56

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,262,880  ·  18 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

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x1d84bebc…07d0

0x34b655…2a6f

4 touches
1 conflict

0x2bc13458…e6d8

0x34b655…2a6f

4 touches
1 conflict

0x2bc13458…e6d9

0x34b655…2a6f

4 touches
1 conflict

0x3413a430…234a

0x34b655…2a6f

4 touches
1 conflict

0x6e859a7c…d0f2

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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 0x13a54fa2d3…a35ae3

← previous block·next block →recent activity