← previous blocknext block →recent activity

Analyzing

Block #85,793,099

21 transactions · 17 stateful · 2026-07-05 16:05:18 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.62

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,793,099  ·  21 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

0x13a54fa2…5ae3

0x2a68ba…90c5

8 touches
6 conflicts

0x62f70d5f…506b

0xd32edf…ff58

5 touches
3 conflicts

0xd025d7d7…f05a

0x3bd359…433a

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…0000

0xd5b70d…615b

4 touches
1 conflict

0x00000000…0002

0xd5b70d…615b

4 touches
1 conflict

0x00000000…0004

0xd5b70d…615b

4 touches
1 conflict

0x18aed20c…48f3

0x000000…012a

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

6 conflicts on slot 0x13a54fa2d3…a35ae3

← previous block·next block →recent activity