← previous blocknext block →recent activity

Analyzing

Block #86,623,663

23 transactions · 14 stateful · 2026-07-09 12:31:46 UTC

Parallelism

87/100

Blocked

43%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,623,663  ·  23 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

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x01a08f7d…dec6

0x34b655…2a6f

4 touches
1 conflict

0x1175233a…64e7

0x34b655…2a6f

4 touches
1 conflict

0x12573732…e891

0x34b655…2a6f

4 touches
1 conflict

0x22bc4ea4…5c8a

0x34b655…2a6f

4 touches
1 conflict

0x31af7f2d…6668

0x34b655…2a6f

4 touches
1 conflict

0x6b2ba712…0214

0x34b655…2a6f

4 touches
1 conflict

0xb1bac7b3…d93e

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

1 conflict on slot 0x13a54fa2d3…a35ae3

← previous block·next block →recent activity