← previous blocknext block →recent activity

Analyzing

Block #86,052,232

27 transactions · 19 stateful · 2026-07-06 20:53:31 UTC

Parallelism

85/100

Blocked

32%

Avg conflicts / tx

0.3

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,052,232  ·  27 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xcc8faac2…c766

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0002

0x04fdea…47d7

4 touches
1 conflict

0xa605468c…1bfc

0x69df8a…6292

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x18cf3003…51d1

0x065c9d…c394

4 touches
1 conflict

0xb1f0701d…4f4a

0xc8689a…ee79

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